You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Problem: I have a custom field added to an Issue Type (Bug) in a Jira Project on it's own Screen and Screen Scheme. When I move this to the same Issue Type (Bug) in another Jira Project with a different Screen and Screen Scheme that doesn't include this custom field I was hoping to be prompted to map this required custom field in the source project to a another field in the target project. Both projects are using the same fields and field configurations. I'd like to avoid adding this custom field to the target project if possible. And the move action does seem to evaluate the fields for the issue type in both projects.
Thanks in advance,
Hello @Marie Burgess
The Move process does not provide you with a list of all the fields in the Source issue/project to enable you to map their values to alternate fields in the destination issue/project.
Note, though, that if the field exists in the Field Configuration then the data will not be lost. You can still see that data if you execute an issue search and add the field to the List view Columns for the search output.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.