Why Jira Agile is created schema for each project?



I wonder that Jira Agile is created schema for each project.


When I make agile (scrum or kanban) project, follow schema created.

- Scrum Issue Type Schema

- Agile Simplified Workflow Schema

- Scrum Bug Screen Scheme

- Scrum Default Screen Scheme

- Scrum Issue Type Screen Scheme (is this all?)


I wonder why that generated separately.
and if there can map the schema to the schema(default or specified by the administrator) without separate created schema

Please tell me the way.


Thank you.


1 answer

1 accepted

1 vote

Atlassian are moving to delegating more and more to the project owners/leads.  If you have shared reused schemes, then you can't do it - a change in one project would affect others.  So, for some project types, the ones likely to be more flexible, the direction is to separate schemes for them all.

If you want to use shared shcemes instead, you'll need to find or write an addon that provides "project templates" that create projects with your shared schemes instead of creating new ones.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,131 views 6 19
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot