IME this is a problem of policy, not of Jira. Empower teams to administer their own Jira projects and it’s fine. But if you lock Jira down and make people beg to some distant and aloof gatekeeper every time they want to change anything, then it’s a recipe for frustration.
Having IT own Jira administration is great for IT job security and terrible for everyone else.
(Note: old Jira absolutely encouraged a one-size-fits-all approach to administration. Everything was done with the assumption that it would be cross-project, which created a morass of assigning things things. “New” Jira project are more self-contained, and so much easier to configure)
Having IT own Jira administration is great for IT job security and terrible for everyone else.
(Note: old Jira absolutely encouraged a one-size-fits-all approach to administration. Everything was done with the assumption that it would be cross-project, which created a morass of assigning things things. “New” Jira project are more self-contained, and so much easier to configure)