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

Issues expressed in a way that's not directly meaningful to users. For instance a user-visible issue could depend on an internal issue

Everything about logs in Heptapod components, including metrics for now. Could be renamed later to Metrics.

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

🚀 Heptapod Release task list

Must be fixed in final releases (version x.y.z)

Useful for Heptapod to run at a larger scale.

Issues that have been brought to our attention by at least one of Octobus professional support customers

Improvements to submit in some upstream (Mercurial, Gitlab…) or to track in upstream, or to backport then track for removal etc.