You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I manage Jira for a large org and we have Cloud (1800 users), Data Center (8000), and Server (10k+). We have a team of 6 people that manages support, infrastructure (AWS), upgrades, and migrations. Obviously that don't scale well and makes us a potential blocker for the very teams we want to help. In the past we've allowed a large number of Jira admins from other teams in order to enable self-service, but those admins haven't always made good choices about customization and it's led to a bit of a mess.
I'd like to hear how other admins handle this. Cloud has of course added self-service projects, but I'm not convinced those are 100% fully baked just yet, especially with regard to the central admin team's visibility into them.
Some things we've done recently:
What great ideas do you have?
We have a Jira Admin structure to support 5,500+ users, 1,100+ Company-Managed Software projects, 6 Team-Managed Software (Next-Gen) projects in a single Cloud instance and are approaching 1,000,000 issues:
We no longer allow new Team-Managed Software (Next-Gen) projects.
We hold monthly Jira Admin CoP with anyone who is a permanent Jira Admin or is eligible to become a temporary Jira Admin. The topics covered are:
Our strategy included established tailoring guidelines. Any change must maintain a stable, performant Jira Cloud. In addition, tailoring needs to support our internal/external regulations associated with development processes, to support the common Jira metrics, and to identify a value add (i.e. increased efficiency). An efficiency gain needs to balance the long term maintenance required on any tailored/additional configuration element.
Any temporary Jira Admin has to review planned change(s), approach to change(s), and timing of change(s) with one of the SMEs. Risks and consult points with SME are established. Required training prior to granting temporary Jira Admin privileges is based on the proposed change and the individual's competency. We do take advantage of our Premium Sandbox with the temporary Jira Admin privileges.