4 ms·

Fast. Something like max 100 ms page rendering time. Even when your computer is bogged down by screen sharing on a telecon. It just makes everybody anxious on a

Fast. Something like max 100 ms page rendering time. Even when your computer is bogged down by screen sharing on a telecon. It just makes everybody anxious on a meeting when they have to look at the presenter's Jira loading up. If you need to implement a progress bar, the game is already lost. I think one could have a CI test for this right from the start, otherwise it will just gets worse and worse with feature addition. Good and fast search. APIs enabling good integrations. For example with Git/Gitlab/Github. With this one can support for various branch and release processes. Ie "is a ticket or a patch in what versions" is a different question for different processes.

avinashjn 6y ago
Fast pages - agree and working on the < 100ms threshold for all pages Progress bar - had never thought of a loader like this. Good suggestion. Search - right now we are directly hitting the db, maybe we can look at redis/solr as read only mirror going forward. Integrations - can you elaborate on this? How would integrations help?
- Gravityloss 6y ago
  Well, I'm not familiar with your product but for example, if there's a bug #bug-789 reported that affects version 1.2, a developer does a fix to that version with commit message like "fixes:#bug-789", automation in the CI can use the bug tracker API and send information to the bug tracker: version 1.2 contains a fix for #bug-789 now. Or it could even say 1.2 was fixed in patch 1.2.435. Users then could for example ask, I have version 1.2.322, what bug fixes do I get if I upgrade to 1.2.435 (latest). With this information, you could answer that with a view in the bug tracker. But some companies might use a different versioning or patching scheme. So the bug tracker would need to be general enough to support those different processes. The key is integrations.

avinashjn 6y ago

Fast pages - agree and working on the < 100ms threshold for all pages Progress bar - had never thought of a loader like this. Good suggestion. Search - right now we are directly hitting the db, maybe we can look at redis/solr as read only mirror going forward. Integrations - can you elaborate on this? How would integrations help?

Gravityloss 6y ago
Well, I'm not familiar with your product but for example, if there's a bug #bug-789 reported that affects version 1.2, a developer does a fix to that version with commit message like "fixes:#bug-789", automation in the CI can use the bug tracker API and send information to the bug tracker: version 1.2 contains a fix for #bug-789 now. Or it could even say 1.2 was fixed in patch 1.2.435. Users then could for example ask, I have version 1.2.322, what bug fixes do I get if I upgrade to 1.2.435 (latest). With this information, you could answer that with a view in the bug tracker. But some companies might use a different versioning or patching scheme. So the bug tracker would need to be general enough to support those different processes. The key is integrations.