How to migrate affected services (standard field in JSM for changes) between 2 jira cloud instances

[Vincent Kopa _Ovyka_]

Hello community :-)

How to migrate affected services (standard field in JSM for changes) between 2 jira cloud instances ?

We need to merge two cloud instances, but it seems that the "Affected Services" field isn't supported by the Jira Cloud Migration Assistant (JCMA), as the services values are empty in the target project (services tab configuration), and also not copied ticket to ticket.

Is this field not supported by JCMA?

If it's not supported, can we use the REST API to

1. copy configurations to the destination project ?
the REST API seems lacking (only a  GET method): https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-service-registry/#api-rest-atlassian-connect-1-service-registry-get 

2. transfer values from ticket to ticket (source to destination) using a Python script?

If we have at least 2. we could do 1. manually, then update the values in all the migrated tickets using a script.

Thank you in advance for your assistance.

[Vincent Kopa _Ovyka_]

Our current situation for this:

1. we've had to manually recreate the Services: Although they use Assets, they're in a locked schema where you cannot setup any import... (so not even through the REST API I think)

2. we can sync the Services field as any other field using a script, but it's more complex as it's kind of an "Assets" field.

I haven't found any better solution yet, I'm still willing to test better things if someone has any better idea.

[Fabian Lim]

Hi @Vincent Kopa _Ovyka_

Have you tried using this: https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?hosting=cloud&tab=overview

It's a great app from appfire @Cody Wooten _Appfire_ 

[Vincent Kopa _Ovyka_]

Hi @Fabian Lim , thanks, we're partners with Appfire, and their apps are very good indeed. 

JSM is only marked in the roadmap though, and I didn't find any mention of Assets (holder of the "Services") or Services.

cf. for reference:

• https://appfire.atlassian.net/wiki/spaces/CMJC/pages/560890337/Product+roadmap+Cloud-to-cloud+configuration+deployment+use+case 
• https://appfire.atlassian.net/wiki/spaces/CMJC/pages/1160020327/Migrate+Service+Management+projects+to+the+Cloud

[Fabian Lim]

To be honest, the best way to go is to do what you mention on the post.

1. Make sure you are in premium JSM in the target

2. Transfer the services through api or even a object import over so that the options are available.  

3. Export the tickets into a csv.  Use excel to match and populate the service to the new service field, most likely you may have to enter the "Key/ID" of the new services in a new column".

4. Import the tickets with the bulk import.