Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to identify duplicate Issue Type Screen Schemas?


I have 12 Issue Type Screen Schemas that are called "<project code>: Kanban Issue Type Screen Scheme". They are presumably all duplicates and I would like to consolidate them so that these projects use a single Issue Type Screen Schema.

How do I confirm that they are indeed duplicates? I would like to ensure that I do not remove someone's Issue Type Screen Schema if it is not a duplicate.

2 answers

1 accepted

0 votes
Answer accepted
John Funk Community Leader Dec 15, 2020

Hey Steve,

What I would do is start by creating a common Issue Type Scheme that has the issue types that you want to use on a project. Then go to the project settings for each project one at a time and compare what is already there with the new. If they line up or the new one is better than the existing, then simply replace the existing scheme with the new scheme. 

Once you have made a pass through the projects, you should have a good set using the same scheme. It will be worth the effort to cut down on maintenance and confusion. 

Then moving forward, I would create projects based on existing projects where you can so that all of these "duplicate" schemas don't get created. The new projects will simply use the shared schemes when the project is created. 

Thanks John,

I have just finished making that first pass and things look more manageable. My plan now is to define logical groups of projects with identical needs and amalgamate every project in the group to use the same configurations so that as you say it will be much easier to manage in the future.

Like John Funk likes this

Looking at the issue closer, it appears that I need to start at the bottom of the hierarchy for duplicates. So I need to identify duplicated screens, then screen schemas then duplicated issue type screen schemas. 

So my question would be how do I identify duplicate screens, duplicate screen schemas and duplicate Issue Type Screen Schemas. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

868 views 14 20
Read article

Community Events

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

Events near you