You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you can only choose one specific issue set. It is pretty hard to create actual good sets that differ from each other so much, that it pays off to create a independent set. Often there is only a small variation between two sets and there is a lot of redundancy. We at codeberg think that modularization of those sets would be a huge advantage for both the admin and the end-user. Modular in this case means that the user can choose multiple sets to create their own label set. As an admin you would then create multiple sets that fit to a major category.
Example
Priority: Critical, High, Medium, Low
Status or State: Backlog, ToDo, Work in Progress, Review, Done, Closed
Kind or Type: Bug, Documentation, Duplicate, Enhancement, Feature, Question
Tag: good first issue, help wanted, invalid, wontfix
Pretending that a user Alice wants to have Kanban (Status) and Prioritization. She simple checks Priority and Status and voila she has all labels from those two sets.
Bob on the other hand does not need Prioritization but he picks Status and Type. His repo will be provided with all the labels from those sets.
Summary
Both the end-user and the instance admin would benefit from this system. The admin only needs to set up some basic sets instead of a ton of sets with only small variations and the end-user can configure their labels the way they want it.
The text was updated successfully, but these errors were encountered:
Introduction
Currently you can only choose one specific issue set. It is pretty hard to create actual good sets that differ from each other so much, that it pays off to create a independent set. Often there is only a small variation between two sets and there is a lot of redundancy. We at codeberg think that modularization of those sets would be a huge advantage for both the admin and the end-user. Modular in this case means that the user can choose multiple sets to create their own label set. As an admin you would then create multiple sets that fit to a major category.
Example
Priority:
Critical
,High
,Medium
,Low
Status or State:
Backlog
,ToDo
,Work in Progress
,Review
,Done
,Closed
Kind or Type:
Bug
,Documentation
,Duplicate
,Enhancement
,Feature
,Question
Tag:
good first issue
,help wanted
,invalid
,wontfix
Pretending that a user Alice wants to have Kanban (Status) and Prioritization. She simple checks
Priority
andStatus
and voila she has all labels from those two sets.Bob on the other hand does not need Prioritization but he picks
Status
andType
. His repo will be provided with all the labels from those sets.Summary
Both the end-user and the instance admin would benefit from this system. The admin only needs to set up some basic sets instead of a ton of sets with only small variations and the end-user can configure their labels the way they want it.
The text was updated successfully, but these errors were encountered: