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
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
When we migrate our Jira Server instance to our new Cloud instance, we have fields that are renamed with (migrated), this is also the case for default field configuration where we have two DFCs...
How to avoid this behaviour?
FYI : The fields concerned are "Start date", "Severity" and "Team".
Hi David. This happened to us when using JCMA to do our test migration from server to cloud sandbox. The Migrated on date also gets added to the description of all the custom and system fields. Not sure if you have noticed this with your migration.
We will be doing a cleanup ourselves to remove the word migrated from the names. Atlassian is helping us remove the migrated on details from the description of the fields but cannot get it right on the Create screen where the details are still appearing.
Perhaps log a ticket with Atlassian to help with the cleanup of this.
What process did you use to migrate your data? Did you use Jira Cloud Migration Manager? If so, what version of it?
I heard from a co-worker that handled a JCMA migration recently that they saw the same. They worked with Atlassian support (through their MOVE ticket) to get "some" of it cleaned up.
Hi Have also migrated the data by using the JCMA plugin, post migration Atlassian support engineer has run the script to do this cleanup activity