Re:Ask HN: I am building a bugtracker. What would you like t...
by Gravityloss on Friday April 23, 2021 @07:51AM
(#26913738)
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.
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.