I have a dropdown field that has a different selector list based on which project it is configured to.
Even if I add options 1,2 and 3 underneath the list for Project #2, I can't seem to retain the info when moving tickets from Project 1 to Project 2. How can I best retain the info?
Are both projects - Company Managed Type? If they are Team Managed Type, then the field setup cannot be shared. Thus, the values will not be retained.
However, if your projects are Company Managed Type, then the custom field (assuming Field A is a custom field) is setup in Settings >> Issues >> Custom Fields. The field itself have different context to support both project A and B. If you added option 1, 2, and 3 to the option context for project B, then when you move issues from project A to project B, the field value will automatically be retained.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Company Managed/Team Managed types are only applicable in the CLOUD env. In Data Center (server) env, all projects are company managed.
In Data Center (server), the custom fields configuration are the same as what you get in the CLOUD env Company Managed typed project.
There has to be some differences between the original option value and the new option value that you added for project B context for the same custom field. (i.e. extra space etc..)
Doing the bulk move operation, it should automatically mapped if the values are exactly the same.
After doing more analysis, the best solution is for one to generate an export (CSV) containing the issue key, summary, and the field in question prior to the move from project a to project b.
After the issue is moved from project a to project b, then conduct a CSV update using External System Import to update the field in question value associated with project b's context dropdown value. (even if the values are the same).
Or, you will need to select the appropriate value manually to resolve the internal ID error during the move operation.
I was surprised that it no longer automatically mapped the value during move or bulk move operation.
Thanks for your input and patience.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events