Inkscape Labels Improvement Suggestion
Issue
We have so many labels and still no way right now1 for us to track the complete status of reports/issues at a glance. Only open/closed is shown which doesn't tell much. I was thinking if we can step up our overall label game (i.e. inkscape group included and not just limited to inbox) and make issue tracking more easier.
Ideal Label system
For better labelling, I think their categorisation is must and some more status labels should be added (new suggestions highlighted below). Ideally we should be able to categorise things as:
type
: bug, feature suggestion, support request, documentation, etc.
prestatus
: (for example for type:bug) needs triage, need info, confirmed,
status
: Won't Fix, WIP, Fixed (partially), Fixed (fully) etc.
area
: UI, UX, Inkscape, performance, format compatibility etc.
comment
: need help, need investigation, etc.
recurrence
: every release (to work as a ToDo)
(See inspiration source2 // I ain't mentioning OS (already in Inbox) or Importance (already in Inkscape).
Implementation
To properly implement this kind of label system in GitLab, following are my ideas (in context of current feature-set of GitLab. Plase share if u think there can be some better way of implementation). I have also noted some caveats.
- we use multiple colon pairs ; use type as nested & key/scope, and status as its value {as in :
nested::key1::value1
}
Example:type::bug::needs triage
,type::feature request::needs info
This, when interpreted with open/close of issue, will give complete status info of the issue e.g. Open>bug>confirmed , Closed>bug>Won't Fix , Closed(moved)>bug>WIP
Illustrative example - There is no option to nest existing labels. So, by using this method, we wont be able to filter by (say,)
needs info
only, we must choose some other scope likebug
before. - There is no way by which we can add multiple values to same scope. So we can't implement
area
andcomment
as suggested in ideal, untill something like multi-valued lables (given name by me😅 i.e. dont try searching for this thing) comes in GitLab!
Suggested Label: infrastructure