I have a JIRA 6.1.7.
I have created a new project to merge some other projects.
I like to move all required issues from the old projects to the new one without losing any information. What happens is that when I move issues with custom-fields of the type "Radio Buttons", "Checkboxes" or "Select List", the value of those fields get lost somehow.
The custom-field are available during the move action, but you have to select the value there or you will end up with an empty field.
I have created all schemes including all issues, workflows and custom-fields I need. At this point I have simply added all custom fields to the Field Configurations and Field Configuration Scheme. Also I have added the target project to the scopes of all custom fields.
In my test environment this leads to the fact, that all values will be moved with the given issue.
But in my productive system I will still lose the values.
Does anybody have an idea what I could have missed?
I finally found the solution:
If you move a ticket with sub-task(s) with the normal move option within the issue, you have to choose the values from the list-fields again.
If you perform a bulk-move you can check "Retain" for each value, and if you check it for the given fields the values will be kept.
So finally the question is: why is the behaviour different between the two move options?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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