4 ms·
My understanding of Jira is that it by itself does not suck but it bends over backwards for asinine “business processes” so it is difficult to find an implement
by minot 6y ago
My understanding of Jira is that it by itself does not suck but it bends over backwards for asinine “business processes” so it is difficult to find an implementation in the wild that does not suck.
- singingfish 6y agoI know a little about the inside of the jira sausage factory from second hand reports. It's got the "accrete everyone else's business processes" problem that you mentioned, but it's also got the problem that it's quite spaghetti on the inside as well, probably for the usual reason - startup founders writing lots of code in a hurry and conflating the purpose of the software with its architecture due to being too close to the problem. Compound that with the usual startup-in-growth problem of more people than necessary (with presumably very uneven capabilities) working on the codebase and you've got a recipe for a maintenance problem. I do know that getting put in the jira team is one of the least fun parts of working for atlassian.
- grimblefasten 6y agoI’ve heard this from multiple sources as well. IMHO, atlassian has had lots of opportunity to fix this... they’ve just been too focused on the next shiny object to do the less fun work of refactoring and redesigning the engine layers into something more sustainable.
- tootie 6y agoJIRA is essentially a platform. It is unopinionated and infinitely configurable. This leaves it open to abuse and many orgs will absolutely abuse it. Other products that are popular do very little by comparison. That lets them build a really tight and simple UI but any org with more than vanilla requirements will hit a wall.