JIRA Project configurator issue - mixed case statuses

On the SOURCE instance I have a status called "Signed off" on the DESTINATION instance I have a status called "Signed Off".  The PC creates the project configuration with non complaints (it doesn't create the status because this already exists), but a subsequent project import fails with

The status 'Signed off' is required for the import but does not exist in the current JIRA instance.

Can the PC detect mixed case duplicates and flag as an error in teh verify step? 

 

1 answer

1 accepted

I suppose when you say "a subsequent project import fails" you mean you were using JIRA Project ImportTool to bring project data into the new instance.

In that case, I think this is an inconsistency of JIRA Project ImportTool, because JIRA treats names of statuses and other issue constants in a case independent way. Most important, if you have in JIRA a status called "Signed off" and you try to create another one with name "Signed Off" JIRA will reject it saying that there is another status with the same name.

cannot-create-status-with-different-case.png

I think Project Configurator could detect this condition and warn the user, but that would not solve your problem, unless you could remove the existing status in the target instance before the import. This would not be possible if that status was being used in workflows.

I think a good workaround would be to edit JIRA XML backup files and "fix" the status names there. AFAIK, the status name only appears once in the entity for the status. This is a line in "entity.xml", one of the files that make up the backup .zip compressed file. It appears like this:

<Status id="10000" sequence="7" name="Signed off" description="A new status" iconurl="/images/icons/statuses/generic.png" statuscategory="2"/>

You are correct in saying that the issue is the data importer, not the Project Configurator. I managed to fix this by renaming the status in the source and re-export the data so that it used this name. It would be helpful if these types of conflicts could be identified during the PC import phase as a warning.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 31, 2018 in Marketplace Apps

Marketplace Spotlight: Zephyr

Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...

351 views 0 1
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