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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Today I would like to share a possible way to migrate or merge a custom field during a periodical cleanup.
Possible ways are built-in functionality of Scriptrunner or myGroovy, own code and own yet another alternative way for the complicated situation.
Also,you can follow with next typical steps of cleanup process:
This is my typical process for the cleanup activity.
As an example, let’s do the next real case with screenshots.
Migrate from the Production environment field to Products field. Both fields are pickers.
Where some of options are the same, if you see the small differences, you can change if both need to be merged.
Then under super user which has access to all related projects, create filters with related tickets.
Then I saved the filter with name test_ .
After visiting the Scriptrunner built-in scripts to copy custom fields values.
After verify via preview and run.
Hooray we merged.
After using the new feature (https://jira.atlassian.com/browse/JRASERVER-41269) from 8.11.0, we can adjust the private filters via gui, if it’s needed. And public stuff as well via gui.
Solution architect | DevOps
170 accepted answers