[#1075] - Unify the labels
- Closed
- 9 Mar 2020
- Medium
- Build: master
- # 1075
Steps to reproduce the issue
I just set the label "Information Required" to the issue https://issues.joomla.org/tracker/joomla-cms/19120
Expected result
Labels on Github are the same as on issues.joomla.org and
I can see this label on issues.joomla.org and on Github.
Actual result
I can see this label on issues.joomla.org.
I can not see it on Github.
Yes, but that's exactly what I think is good. Is there a reason why this is not so? I mean, why there are different labels?
If I close an issue on issue.joomla.org, it is closed on github too.
That is why I expected the labels similar too.
The only status in the issue tracker that has a label that is automatically set on GitHub is the "RTC" status. None of the other statuses are also created as GitHub labels.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-06 18:59:27 |
| Closed_By | ⇒ | astridx |
OK. I got it wrong. I thought the labels in github should be the same with the issue tracker status. I would still like that too.
Open again, because Bug Squash Team would like to unify labels on Github and state in Issue Tracker:
Issue Tracker Labels versus Github Labels:
It has been noted that certain labels do not carry over to Github and vice versa between the issue tracker. A request has been opened in the JIssues tracker to synchronize Github labels with the Issue Tracker. This will ensure minimal confusion when PRs are created and new issues are created that labeling is consistent
Would this be possible?
| Status | Closed | ⇒ | New |
| Closed_Date | 2020-03-06 18:59:18 | ⇒ | |
| Closed_By | astridx | ⇒ |
More clarity is necessary here. There aren’t “labels” in the issue tracker
that aren’t synchronized with GitHub’s definition of labels. There is data
in the issue tracker that is not synchronized with GitHub because it
doesn’t correspond to anything on GitHub.
Someone needs to clarify what they are looking for here. Just because
something renders as a Bootstrap label doesn’t mean that it is a label in
the sense of what is defined on the GitHub repository as an issue label.
On Mon, Mar 9, 2020 at 3:38 AM Astrid notifications@github.com wrote:
Open again, because Bug Squash Team would like to unify labels on Github
and state in Issue Tracker:Issue Tracker Labels versus Github Labels:
It has been noted that certain labels do not carry over to Github and vice
versa between the issue tracker. A request has been opened in the JIssues
tracker to synchronize Github labels with the Issue Tracker. This will
ensure minimal confusion when PRs are created and new issues are created
that labeling is consistentWould this be possible?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/joomla/jissues/issues/1075?email_source=notifications&email_token=AACZ7INIPSUEYDJHDHLURITRGSTIZA5CNFSM4LCQPK42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOGE5IY#issuecomment-596397731,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACZ7II2YWAEU52H6CR6IFLRGSTIZANCNFSM4LCQPK4Q
.
--
- Michael Please pardon any errors, this message was sent from my iPhone.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-09 12:30:58 |
| Closed_By | ⇒ | mbabker |
https://github.com/joomla/joomla-cms/labels is everything that should be synchronized between GitHub and the issue tracker as a label. This means they are explicitly set as a label on GitHub or through the “Labels” field on the tracker’s edit screen.
The issue tracker’s concept of categories is not synchronized with GitHub because those are not labels.
The issue tracker’s concept of issue status is not synchronized with GitHub because those are not labels. There is special system handling to set a “RTC” label when the status is set to “Ready to Commit”.
Both of these items, as well as labels, are rendered as Bootstrap labels and badges. Just because they have a similar design does not mean they are GitHub labels.
Closing this as not a bug, because labels (as defined on the repository’s label list) are properly synchronized between platforms. If someone is looking for a system change where other data is set as a GitHub label, please open a new issue with clear information regarding the change request.
if i can be that bridge, i would like to be that bridge
....silly me----
but now i suppose to have a team made of "active peoples"
More clarity is necessary here.
true
can we have a chat on the jbs glip channel ? or in whaterver channel do you prefer ?
The status is "Information Required". This does not arbitrarily set a "Information Required" label on the GitHub item.