Project configurator to use same custom field id as source instance

Olga Mistry

Hi Team,

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.

steps followed:
-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.

• while trying to restore project in test 2 env using "Load project configuration" in other instance, project configurator is creating same custom fields with different custom field IDs.

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.

For example
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.

Thanks
Saurabh Tamrakar

José Marañón [Awnaba Software S.L.]

Hi Saurabh,

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!

 

José Marañón

Awnaba Software