Hi, we are moving from Jira 3.13.2 to Jira 5.2.
We notice that once the backup is complete with the new instance we are having issues with some of our custom fields. The problem is that the option values are different from our old jira instance which is causing us problems.
The select list in the old system for a particular custom field has the following:
But in the new instance the same custom field has the follow:
Can you help us out here please,
Somewhere around version 4.3 (Sorry, I can't remember the exact release), the schemes were changed quite drastically. Before the change, an "option" was a simple string which was stored in the list of options, and then on the issue custom field when you used it. It's been changed to an ID-and-label format - Jira works with the IDs internally, but displays the label. This allows you to rename options, and is more consistent with the rest of Jira.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
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!
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