Earn badges and make progress
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
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
How can I avoid having 'Removed Fields' when switching from one issue type scheme to another?
Hi, I am currently working to switch my project from one Issue Type Scheme to another.
Some of the issue types in the old scheme will not be used in the new scheme. However, to not lose the issues with these issue types in the new structure, I have created placeholder issue types in the new scheme.
Now, at the time of switching the project from old issue type scheme to the new one, I have mapped the issue types that will not be used from the old one to the placeholder issue types and for each of them, I saw a confirmation that the old values will be retained. When I get to the summary step where I review and confirm I see a set of fields that will be removed, how can I avoid these and ensure that all fields in the old issue type get retained in the new placeholder issue type?
1 answer
1 accepted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.