As part of a consolidation I am moving many issues from individual projects into a larger project. Most field values are easily maintained, but fields from the source project that use a unique field context are lost when moved into the new destination project even if those same field values exist in both. Unfortunately, I can not simply add the destination project to the same context because there are many projects using this field all with unique contexts that I intend to move issues from into this destination project.
Did a little digging and found that these fields refer to the field value ID and not the field value itself.As far as I can tell, there is no way to retain these field values (other than in the issue history).
Does anyone have any recommendations? TIA!
If you are moving from one project to another in the same instance, it should be using the same field. Unless you have created multiple custom fields with the same name. Can you verify that? Otherwise, the shared field would be the same field.
One field, many contexts.
Source project 1 context:
Source project 2 context:
Destination project values:
Unfortunately, I can not simply add the destination project to the same context because there are many projects using this field all with unique contexts that I intend to move issues from into this destination project.
Hi @Jonathon S ,
Though not the same issue, the issue you described is similar to the below article and issue
Another tricky solution is to
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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