JIRA is so slow and the UI so clunky the project managers where I work use some type of spreadsheet upload mechanism with XML spreadsheets to automate the cruft creation. It's fun to watch.
Unfortunately, from the project manager's perspective the emphasis is on the words making sure
And Jira lets them think they're doing that
Software developers' mistake is not realizing that "linking the tickets" into Epics that managers can search is hugely important.
If the project director has no clue about what tickets people are working on things go south fast.
All developers should agree on that.
The only reason stuff gets done as it should it because me and my peers are responsible, and because we have a good understanding of what needs to be done, not because of how things are mapped in JIRA.
Jira is the way it is because Jira ISN'T built for developers.
Devs may have to use Jira, but they're not the ones who have to pay for it.
I wrote about this a while back:
"Who is Jira’s target customer? It’s certainly not the poor developer who struggles to add a link to his bug report. (I’m still mad at them)
Take a look at Jira’s site and see what they emphasize:
Those pages glamorize having an overview of what work your employees are doing. It’s a tool made for managers. Especially higher level ones. The VP won’t be filing work items, but they’ll be very interested in the insights those dashboards offer.
Jira spends all their software cycles building new features for that VP, ignoring what you and I might consider critical user bugs."
Source: https://www.zainrizvi.io/blog/never-focus-on-the-user#jira-s...