Thank you for responding with the solution to use
We have downloaded "project configurator". plugin and tried to use the same on our test environment.
It worked as expected with one issue which is holding us back from using the plugin in our production environment.
-we exported all the custom fields used in a project using project configurator & we were able to save the xml file in test 1 env.
As we have created our workflows by modifying the xml files and exporting the same xml in test 2 env, we need same custom field ids( as in test env1) in other environment (test env 2).
Please let us know how this can be achieved.
custom field - "Change in Risk Profile" has event id 11257 in production env.
while same custom field "Change in Risk Profile" has event id 11250 in UAT env after loading project using Project configurator.
PFA screen shot , where custom field id has been changed (newly created) and not same as production custom field id.
Yes, IDs of objects created in the destination instance can be different (and they usually are). The reason is that it is impossible to force that new custom fields are created in a different instance with a given ID (at least from the JIRA Java API). In some cases it would be also logically impossible, when that id is already assigned to a different custom field.
However, that is not a problem when you want to transfer workflows to the same instance. If you transfer them with Project Configurator (this would be the default) the plugin will take care to adapt the IDs of custom fields referenced by the workflow. You need not worry about that.
You are welcome!
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG