Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider renaming legacy-jira-priority: ... to priority: ... #148

Open
vlsi opened this issue Aug 18, 2022 · 1 comment
Open

Consider renaming legacy-jira-priority: ... to priority: ... #148

vlsi opened this issue Aug 18, 2022 · 1 comment

Comments

@vlsi
Copy link

vlsi commented Aug 18, 2022

See #61 (comment)

Sample issue: https://github.com/apache/lucene/issues/1072

I think legacy-jira- prefix makes the label longer, and it does not add extra value.
If you do not intend to use the label for newly created GitHub Issues, then is it really worth carrying the label?
@mocobeta
Copy link
Contributor

mocobeta commented Aug 18, 2022 •
edited
Loading

The label is an intentional one. I think we mark all the Jira metadata with "legacy-jira-" if we don't use them in GitHub, not to bloat labels from the start.
We prepare minimum predefined labels for GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vlsi @mocobeta