nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to identify duplicate Issue Type Screen Schemas?

Steve M

Hello,

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.

Accepted answers

John Funk

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.

All comments

Steve M

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.

John Funk

Hey Steve,

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.

Steve M

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server