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
There was a question about the correct transfer of the workflow from the test Jira to production, which has the same workflow, but without the improvements that were added to the test copy of the workflow.
I'm export the workflow file as a JWB file on test Jira and import it on production. During loading, Jira creates duplicate custom fields and screens that participate in the workflow, which is very inconvenient, because you have to manually remove these duplicates and adjust the workflow to match the original custom fields and screens.
Is there a mechanism to load a workflow modified on test Jira so that custom fields and screens that already exist are not created as duplicates, but are used by default, so that only those that are not present on the Jira instance on which the workflow is loaded are created?
The documentation doesn't say anything about this.
Unfortunately, out of the box this is not possible.
However, there are plugins such as project configurator (https://marketplace.atlassian.com/apps/1211147/project-configurator-for-jira?tab=overview&hosting=datacenter) or Configuration Manager (https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?hosting=cloud&tab=overview)
Both of them do the job especially when you have a dev and prod instance to migrate approved changes.