Duplicate custom fields

Chris July 22, 2020

 

 

I am trying to promote one of my project from Dev to Test using configuration management but while deploying I find duplicate custom fields there. The custom field showing here is not getting used for my this project in source Environment. Could you please help me how to find out where this custom field is getting used in my project.

CM.PNG

 

1 answer

0 votes
Sachin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2020

Hello @Chris , you can do two things

1. Goto your source Jira and temporarily rename the custom field before creating the snapshot (I wouldn't recommend doing this if this is on production and being used by other projects)
2. Edit your xml file and remove that customfield and zip back the files and try deploying again

To find the custom field on your source Jira, you can goto this URL: https://instancename/jira/secure/admin/ConfigureCustomField!default.jspa?customFieldId=10000
, there you will find in which projects the Custom Field is being used and what context does custom field has.

Note: Replace the instance name and customfield ID from above URL

Chris July 22, 2020

Thanks for your reply.

1. My xml was corrupted after removing that custom field.

2. The url takes me to the configure custom field. It is a global field. Is that the reason you feel my project is using it?

Sachin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2020

XML changes can be tricky, as you need to look for the right parameters. Anyways, lets look at the second option.  A global field is something that's being used globally (which is also being used by your project).

You can run a JQL: "CustomField" is not EMPTY to see how widely it's used. If it is not used in projects, you can rename the custom field temporarily and get new snapshot and continue your deployment.

Looks like you can Resolve the custom field conflicts as per https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/48431112/Resolving+Custom+Field+Conflicts

Make sure you are on version 3.5 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events