Jira has a bit of a confused approach to settings. One the one hand, we've got every admin on the planet yelling "keep it simple, share config, keep your processes consistent or you will make a mess" and then a load of process people yelling "let everyone do whatever they like and run their projects however they like"
So there's a bit of a conflict. Admins want people to use "shared configuration" as much as possible, but Atlassian have gone with "create your own projects" and that means using separate configurations for every new project.
You will want to strike the right balance for your organisation and train your admins to do the right thing. As an example, one organisation I worked for a while ago had thousands of schemes and was in a right mess. It took a while, but we got it down to "90% of projects should be created with one of 5 (shared) configurations, and the other 10% are all going to need their own setup independent of the others". That was right for them, you might have different needs.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events