3 ms·
Every large scale software system needs a ticket system if some kind. You might separate the backlog from the bug reports, or omit one part, but you'll have som
by alkonaut 10y ago
Every large scale software system needs a ticket system if some kind. You might separate the backlog from the bug reports, or omit one part, but you'll have something.
You can't find the reason for a change otherwise, you can't find all the related changes for the feature, you can't catalog incoming bugs and answer whether the last bug report must be tackled or has already been fixed and so on.
This is why - like it or not - there always is an issue management system. It's on a server somewhere, or in an excel sheet, or emails, or on a piece of paper. But it's there.
The usual criticism of Jira is that it's heavyweight compared to e.g GitHubs issue tracker, or whatever post-it moving system is the latest fad.
A fair criticism of Jira is that it makes it too easy for management to encode and expand the formal rules for e.g task workflows, and that these rules invariably end up being too rigid.
An organization should have the least invasive workflow it can, but it should encode and enforce the workflow.
In the end, just like you always have an issue management system, you also have a change workflow. Either it's encoded formally using an issue/PR system or it's ad-hoc via chat and email (which scales very well up to around 2 developers but shows it's weaknesses already at around 3)
- prodigal_erik 10y agoThat's the main failure mode I've seen. An over-engineered and role-limited workflow in which the real-life state of the project is considered invalid or nobody is authorized to express it.