There have been various questions about how many administrators are need for an environment. Want to give some specifics about our environment and ask again. The team I am on is responsible for Data Center: Jira Software, Confluence, and Bitbucket. Also responsible to build and maintain the infrastructure they run on.
I would consider all the instances to be large do to the integrations, number of users, projects & number of issues in Jira, spaces & pages in Confluence, and projects, repos, and code in Bitbucket. Started using these products ~7 years ago and usage & adoption continues to grow.
How many full and part time administrators do feel should be allocated for support? Please share the specifics about your organization and how many administrators you have allocated.
1 full time administrator and 2 part time
@Matt Rice - Yowza, +50 apps in your Confluence instance? Nice.
You wrote “5 node clusters in 3 Data Centers. Only 1 active.” - can you elaborate or rephrase this? I’m not understanding what this bullet means.
Agree with @Dave Rosenlund _Trundl_ as well as some other things
Standards
Governance
SCM controls
What else is the team responsible for ? ex: DevOps... Build/Release Management
How complicated are the projects / workflows based on the integrations you've listed above.
How much control are users given to manage their own processes?
How much is shared across the tools.
This is a great topic, @Matt Rice . I can give a baseline that is a fundamental beyond the salient points raised by @Craig Nodwell and @Dave Rosenlund _Trundl_ ...
UNLESS the environment is dead simple and is NOT likely a blocking factor to work being done, two. Having been a SPOF in a busy and complex environment, it really sucked going on vacation as I had to put a moratorium on changes well in advance of planned absence and I knew that the "urgent" needs would just have to wait.
After that... experience and creativeness of the admins extant comes into play. At one of my last spots, our TPM claimed I was better and faster than all the admins together at his previous shop. Perhaps he was being nice but I know I was able to turn some stuff quicker than anyone expected.
So... Start with two minimum and then see how bad/fast the backlog grows
For the basic everyday tasks like adding users to groups/projects etc we managed to get general IT support to pick those up to let us admins focus on the more difficult stuff. They had to have admin rights but fortunately they are easy to work with and stay in their lanes.
It depends. 😅
I started a discussion about this back in July 2021 ("how many Jira admins does it take to screw in a lightbulb"), which got 9 comments:
Only one but you need to buy the light bulb app
Hopefully there's a Data Center version!
AND that the Cloud version isn't missing critical features.
Researched, and apparently Lightbulb for Jira Cloud is nested under the global Apps menu instead of having a native panel in the issue view... c'mon Atlassian!
Great discussion @Matt Rice and @Dave Liao
We have one JIRA admin for our whole IT department. I have to imagine he is a bit overwhelmed.
A follow up question: Should being a JIRA admin be a full time job or should it be part of someone's job? I've seen it both ways.
depends on a number of factors, though the list isn't inclusive of all factors:
1) How many users?
2) Are projects using different Screen, Workflow, Issue Type Schemes, etc.
3) How many Custom fields?
4) How many Addons?
The more complex a Jira instance, the more Jira Admin support is needed.
When scanning client environments, I never encountered less than five.
Two is a minimum, maximum five I would say.
Great topic, @Matt Rice !
It's interesting to see that I'm not the only one who is the sole admin. I wear many hats (Jira admin, Confluence admin, Crowd admin as well as other ancillary products managing almost ALL aspects of system administration for nearly 3000 users at it's peak -- configs, development, testing, documentation, governance, user training, hardening, upgrades/patches, research and implementation of new add-ons and processes, etc.) and feel that I can be MUCH more effective if I had a team of admins.
Until recently, we had another sys admin who was awesome and helped alleviate some of the load but I've found that the majority of my time is spent educating users (we are a very white-glove service-first oriented company) on best practices and usage of the applications, despite having a wealth of documentation and how-to videos available. While this is great and is common for SMEs, it also doesn't afford much time to focus on improving processes. Even with the automation and off-loading of certain BAU activities, it's still A. LOT.
For those of you out there who also have limited team resources, how the heck do you not get burned out (or are you and just continuing on)? It's exhausting!