10 ms·
> The defaults even way back when actually made quite a bit of sense. The default workflow for many project types were very workable. That's probably where the
by CRConrad 4y ago
> The defaults even way back when actually made quite a bit of sense. The default workflow for many project types were very workable.
That's probably where the wide-spread (and arguably correct) impression that it has become worse comes from: To begin with, people just installed and used it as-is, but by now corporate bureaucracies have had time to "implement" it -- i.e. set it up -- to mirror their organisation's bureaucratic structure and processes.
And yes, that impression is correct; it is Jira's fault: If it didn't have that customisability, they couldn't (ab)use it that way.
> If your organization chooses to instead use this very very configurable tool to lock things down you can't blame Jira.
Of course you can: If it didn't offer the possibility to set up those bureaucratic locks, they wouldn't be set up.
- tharkun__ 4y agoI can tell you that a lot of other tools before Jira that I have had to use were really quite good at mirroring that structure in a much worse way ;) Most of those tools from my experience were not usable in a good way. You and other people are obviously entitled to the opinion that Jira made it worse. In my book, that's like saying it's the Swiss Army knife's fault that someone was killed with it.
- CRConrad 4y agoVictorinox's fault. If there were no Swiss Army knives, nobody would get killed with one.