Ask HN: I am building a bugtracker. What would you like to see?
<p><pre><code>  - FAST web interface, being able to go from issue ID to browsing it, to replying in less than a second.
  - Dense, text-centric web interface. Whoever will use the tool will use it often enough that the UI should value utility over style.
  - Fast, rich search, with fuzzy full text search and key:value syntax (eg.: author:foo, status:closed, etc).
  - Single, flat namespace of issue IDs, preferably numeric, and the ability to follow a single issue ID as it&#x27;s moved across boards&#x2F;categories.
  - Low friction update&#x2F;create UX. Users should file issues early and often.
  - First class email integration - replying to issues via email should be as good as replying via web UI. No &#x27;write above this line&#x27;, make it smart. The issue tracker should basically eradicate the need to have private email conversations.
  - Unopinionated hierarchical category&#x2F;component system, with per category customization of authentication. No fixed project -&gt; board -&gt; epic -&gt; story -&gt; task nonsense, let me adapt the tracker to my flow, not the other way around. And especially no fixed code repository &#x2F; category relationship. And finally, no, tags are not a replacement for this.
  - High quality API for automation. Features like kanban boards and other &#x27;higher level&#x27; constructs for managers should be implemented using this API, so that users can modify and implement their own &#x27;views&#x27; as needed, instead of relying on some fixed functionality.
  - On premise, cloud-native deployment, eg. backed in cockroachdb. Cross-region failover&#x2F;sync for geo redundancy.
</code></pre>
(context: I hope to have time to finish <a href="https:&#x2F;&#x2F;github.com&#x2F;q3k&#x2F;bugless" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;q3k&#x2F;bugless</a> some day, or that someone just beats me to it)