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.

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

Label priority score #9401

Open
lunny opened this issue Dec 18, 2019 · 5 comments
Open

Label priority score #9401

lunny opened this issue Dec 18, 2019 · 5 comments
Assignees
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@lunny
Copy link
Member

lunny commented Dec 18, 2019

Every label could be given a priority score which is default 0 for compitable. When list issues or pull requests, there is a new option to list according label scores.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Dec 18, 2019
@jolheiser
Copy link
Member

This sounds similar to issue priority. What would be the difference, just more granular?

@lunny
Copy link
Member Author

lunny commented Dec 18, 2019

@jolheiser It's not the same. You could create three labels, high priority, normal priority and low priority and give 3, 2, 1 score. That it is.

For issue priority, you have to change one by one issue and it's difficult to decide which issue's more prior than another.

For issue, we could have a pin issue feature.

@zeripath
Copy link
Contributor

Presumably you mean that the score of the issue would be the sum of its labels?

Would you want to sort by this score?

@lunny
Copy link
Member Author

lunny commented Dec 19, 2019

@zeripath yes

@lafriks lafriks added type/feature Completely new functionality. Can only be merged if feature freeze is not active. and removed type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Dec 19, 2019
@lafriks lafriks self-assigned this Dec 19, 2019
@stale
Copy link

stale bot commented Feb 17, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 17, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Feb 17, 2020
@stale stale bot removed the issue/stale label Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

4 participants