The labels (imo) appear to be a mess and I’m proposing to reorganize them (a task I’ll definitely assign to myself as related to issue grooming stuff). Can people confirm if any of the redundancies are intentional and how we can optimize this system which is quite important to issue grooming and organization of our tasks.
We don’t have scoped labels (unless we pay for the bonus feature which I agree with @salt that we shouldn’t) but there are definitely workarounds and other ways of categorizing labels in hierarchies (note that there are ‘prioritized labels’ as well. I don’t have as much experience as others who have worked on projects that have many subgroups, so any insight here is great.
This was a little tedious as I had to do this by hand but these are our labels currently (may have made mistakes but I was pretty thorough and double checked - still confusing though with number of labels and how they appear).
Here is a list of our current labels (for the listed subgroups, there’s still more smh)
Note the redundancies! Every project (or subgroup) has it’s own “project labels” and also has access to the labels of the ‘group labels’
- Snowdrift.coop Group Labels:
- do next
- top priority
- high priority
- medium priority
- low priority
- needs grooming
- blog article
- dev tooling
- gathering specs
- needs clarification
- new feature/design
- patches welcome
- gather specs
- gathering specs
Random note: searching for an issue with the title ‘label’ isn’t possible
Helpful note @wolftune: if you want to filter out a certain label you don’t want to see, type “label” and then “!=”
It seems like we need to get rid of redundancies OR if intentional rename those redundancies in a way that makes it clear to which group it belongs to.