Pros and Cons of individual or shared project configuration

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

  1. create one shared configurations of workflows, issue types and screens and use it mandatory on all projects
  2. have an individual configuration per project

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?


For 60 projects I would recommend #1, or create a small set of schemes. If you follow #2 you will spend more time updating every scheme in the future

It's the difference between a deli and a supermarket!

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.


Log in or Sign up to comment
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

998 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you