JIRA might be like C++. It's OK if you just use a subset, and everyone uses the same one. If you use all of it, though, you get a mess.
The fundamental problem with JIRA is that it's trying to be usable for all the workflows in all companies in all the world. It's hard to do that simply.
And the problem with using it is that companies don't fix their workflow; they just try to port their existing workflow to JIRA. The result is that all the frustrations with the workflow turn into "frustrations with JIRA" (on top of the frustrations that are actually due to JIRA itself).
Comments
JIRA might be like C++. It's OK if you just use a subset, and everyone uses the same one. If you use all of it, though, you get a mess.
The fundamental problem with JIRA is that it's trying to be usable for all the workflows in all companies in all the world. It's hard to do that simply.
And the problem with using it is that companies don't fix their workflow; they just try to port their existing workflow to JIRA. The result is that all the frustrations with the workflow turn into "frustrations with JIRA" (on top of the frustrations that are actually due to JIRA itself).