Although subjective, this'll be useful
Something doable without learning much about the project structure, perhaps just a grep away. Many UI issues fall in that category.
Yes, it's subjective, a lacking feature can be a bug, we'll see
All grunt work about tests, build system, version bumps of upstream GitLab, Mercurial etc.
For issues about which the wished behaviour still needs to be discussed
For issues related to Git projects
Issues related to the move to Mercurial native support – the whole HGitaly project being currently about that, no need to put it on all HGitaly issues
Denotes a disruption to IT services and the associated issues require immediate attention
heptapod / omnibus-heptapod
Issues expressed in a way that's not directly meaningful to users. For instance a user-visible issue could depend on an internal issue
For bugs that apply to some projects / instances only and whose systematic reproduction is not known yet
For issues whose original author would have to be picked in previous Heptapod self-hosting instance
A bug that didn't occur in earlier releases, usually deemed worse than a bug on new features
Must be fixed in final releases (version x.y.z)
Useful for Heptapod to run at a larger scale.
Improvements to submit in some upstream (Mercurial, Gitlab…) or to track in upstream, or to backport then track for removal etc.
Issues in scope for the July 2020 virtual sprint https://framadate.org/heptapod-vsprint-2020-07
Virtual Sprint, October 2020