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.
Hi JIRA administrators,
It would be great if you could share your experience of using JIRA for 60+ projects without having a mess in all that schemes.
Is it better to
Right now I am mostly for #2, as it has big flexibility for each project without affecting others, but I will have 60+ configurations that probably noone exept me could deal with.
What is your experience?
Matt, thank you, I like your comment.
So does this mean that for 60 projects we should say that "company rules" are over team's agility? Instead of allowing teams to try their own way they should just select one scheme from a set because it saves administrators time.
Does any one know how do the very valuable shared configuration in the new jira experience? That options has disappeared among the new project creation screens.
I had over 50+ project to manage, i had a mix of 1. and 2. The Business unit was the common denominator. I was sharing the same configuration within a business unit but each unit had it own configuration for security purpose.