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.
Hello,
I am in a situation where different projects on Jira are working on very different field configuration schemes.
In order to align them, I have created a default field configuration scheme that fits best the company's needs.
However, I have to now migrate the projects to the new scheme I have created.
What is the impact of this on projects? Will they lose their data if for instance on of their existing fields does not exist in the new field configuration scheme?
Hi @Rasha Alshatti,
Welcome to Atlassian Community!
Existing data will not be affected, unless you delete custom fields or change the values available.
Thank you Mikael!
This means that if:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Rasha Alshatti !
I'm wondering if you were able to successfully migrate your projects to the standardized field configuration scheme you created and if all data was retained from projects on the deprecated field configuration schemes?
(I'm assuming from your initial question that the new field configuration scheme included fields specific to different schemes.)
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.