I tend to agree Jira is a bit of a mess, but the responsbility needs to be shared with the users.
- Why buy a complicated mess?
- Why let a random Scrum Master / Product Owner manage it?
- Why don't we think we need to protect an IT system we buy like an IT system?
Many of the reasons engineers hate Jira are specifically related it being a complicated mess that is hard to use and admin. So if management would listen to engineer about IT systems, maybe this wouldn't happen?
Another possibility is we actually did a risk assessment and what we put in Jira isn't of sufficent risk for us to care, so actually IT doesn't need to be involved because we're not super worried about it leaking.
There are likely worlds of both involved.
My own pet hate is just that it's too slow and often configured in a convoluted way that makes me spend too much time in it.
- Why buy a complicated mess? - Why let a random Scrum Master / Product Owner manage it? - Why don't we think we need to protect an IT system we buy like an IT system?
Many of the reasons engineers hate Jira are specifically related it being a complicated mess that is hard to use and admin. So if management would listen to engineer about IT systems, maybe this wouldn't happen?
Another possibility is we actually did a risk assessment and what we put in Jira isn't of sufficent risk for us to care, so actually IT doesn't need to be involved because we're not super worried about it leaking.
There are likely worlds of both involved.
My own pet hate is just that it's too slow and often configured in a convoluted way that makes me spend too much time in it.