Label priority score #4507

New Issue

GiteaMirror · 2025-11-02T05:52:57-06:00

GiteaMirror commented

2025-11-02 05:52:57 -06:00

Originally created by @lunny on GitHub (Dec 18, 2019).

Originally assigned to: @lafriks on GitHub.

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.

Originally created by @lunny on GitHub (Dec 18, 2019). Originally assigned to: @lafriks on GitHub. 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.

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 05:52:57 -06:00

GiteaMirror closed this issue

2025-11-02 05:52:57 -06:00

GiteaMirror commented

2025-11-02 05:52:58 -06:00

@jolheiser commented on GitHub (Dec 18, 2019):

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

@jolheiser commented on GitHub (Dec 18, 2019): This sounds similar to issue priority. What would be the difference, just more granular?

GiteaMirror commented

2025-11-02 05:52:58 -06:00

@lunny commented on GitHub (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.

@lunny commented on GitHub (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.

GiteaMirror commented

2025-11-02 05:52:58 -06:00

@zeripath commented on GitHub (Dec 18, 2019):

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

Would you want to sort by this score?

@zeripath commented on GitHub (Dec 18, 2019): Presumably you mean that the score of the issue would be the sum of its labels? Would you want to sort by this score?

GiteaMirror commented

2025-11-02 05:52:58 -06:00

@lunny commented on GitHub (Dec 19, 2019):

@zeripath yes

@lunny commented on GitHub (Dec 19, 2019): @zeripath yes

GiteaMirror commented

2025-11-02 05:52:59 -06:00

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.

GiteaMirror commented

2025-11-02 05:52:59 -06:00

@wxiaoguang commented on GitHub (Apr 15, 2025):

Done in 1.24

@wxiaoguang commented on GitHub (Apr 15, 2025): Done in 1.24

GiteaMirror referenced this issue

2025-11-02 13:15:45 -06:00

[PR #4533] [MERGED] Don't fail silently if trying to add a collaborator twice #17415

GiteaMirror referenced this issue

2025-11-02 13:37:40 -06:00

[PR #4748] [MERGED] Allow to add organization members as collaborators on organization owned repositories #17484

Sign in to join this conversation.