Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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.

Atlassian Community about banner
4,464,103
Community Members
 
Community Events
176
Community Groups

Migration of projects from a field configuration scheme to another

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? 

1 answer

1 accepted

0 votes
Answer accepted
Mikael Sandberg Community Leader Nov 29, 2022

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:

  • I have a custom field drop down list with the values 1 and 2
  • and I have an issue where this field is equal to 2

    > then if modify the configuration of this custom field and remove the value "2", my existing issue where this field was defined as 2 will be empty? even if it is mandatory? 

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!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events