Hi, we have saveral duplicated fields in our JIRA. Here the list with the amount of duplication in brackets. Epic Colour (3) Epic Link (3) Epic Name (3) Epic Status (3) Raised During - JIRA Capture Test Session (2) Rank (9) Sprint (8) Story Points (2) First question: * How to identify which custom field is used and needed and which can be removed? To prevent some answer I can add that filtering in Issue Navigator is pointless because it always shows the same value equals all issues in JIRA Second question: * Some of them are marked as Obsolete and some of them are locked. Does it mean that obsolete are no longer used and can be deleted and locked are still in use?

You can check how to get rid of the duplicate fields using the following KB: * https://confluence.atlassian.com/display/AGILEKB/How+to+Fix+the+Duplicate+Agile+Custom+Fields+After+Upgrading Cheers, Andre

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; } } }

Identify and delete duplicated custom fields

Hanna Kutkowska1

Hi,

we have saveral duplicated fields in our JIRA. Here the list with the amount of duplication in brackets.

Epic Colour (3)
Epic Link (3)
Epic Name (3)
Epic Status (3)
Raised During - JIRA Capture Test Session (2)
Rank (9)
Sprint (8)
Story Points (2)

First question:

How to identify which custom field is used and needed and which can be removed?

To prevent some answer I can add that filtering in Issue Navigator is pointless because it always shows the same value equals all issues in JIRA

Second question:

Some of them are marked as Obsolete and some of them are locked. Does it mean that obsolete are no longer used and can be deleted and locked are still in use?

Accepted answers

petry

You can check how to get rid of the duplicate fields using the following KB:

https://confluence.atlassian.com/display/AGILEKB/How+to+Fix+the+Duplicate+Agile+Custom+Fields+After+Upgrading

Cheers,
Andre

All comments

Nic Brough -Adaptavist-

First question

Change the name of the fields - just add a . to the display name or something clear like that.
Run a filter for each one (e.g. "Epic Link is not empty", "Epic.Link is not empty", "Epic..Link is not empty" ). You can kill off any that return 0 results.
Where you have results in more than one, you'll need to analyse your data and work out which one is best to keep and what to merge in before you can delete them

Second question

Obsolete ones can probably be junked
Locked ones you probably want to preserve - they're a bit of a pig to remove

petry

You can check how to get rid of the duplicate fields using the following KB:

https://confluence.atlassian.com/display/AGILEKB/How+to+Fix+the+Duplicate+Agile+Custom+Fields+After+Upgrading

Cheers,
Andre

Hanna Kutkowska1

Thanks You both!

Nagendra Babu_xjlnnl

Guys we can a very useful plugin which shows a clear view about used and unused Custom fields

Custom field Usage for jira

H K_e8dn1j

Hi @petry

Due to the the recent JIRA migration from company "A" to our company "B", there have been over 50 custom fields that were moved across and have more duplicated in our company "B" instance.

There are over 3,000 custom field around there. So, how can I find the duplicated fields which I don't know their names, and then delete the migrated fields?

Could you please assist me on this?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration