2
1
0
1 answer
- 10-1
Migrating a connection configuration
> Is there going to be heavy script modification
How long is a string?It all depends on the integration that you have in the current connection.
The Exalate API is pretty identical on both platforms, but some items might be different.
Give it a try and let us know.Migrating the connection data
With the new connection you will have to reconnect the issues using the bulk connect
Bulk Connect
This function expects a csv file containing the local and remote issue keys.
So you would need to extract this information in some way.One of the ways is using SQL - here you have an example in postgres dialect
Getting all twins from a connection Expand sourceSELECT LR."ISSUE_URN" AS localissuekey, RR."ISSUE_URN" AS remoteissuekey FROM "AO_08F1AF_TWIN_TRACE" TT LEFT JOIN "AO_08F1AF_REPLICA" LR ON TT."LOCAL_REPLICA_ID" = LR."ID" LEFT JOIN "AO_08F1AF_REPLICA" RR ON TT."REMOTE_REPLICA_ID" = RR."ID" JOIN "AO_08F1AF_RELATION" R ON TT."RELATION_ID" = R."ID" WHERE R."NAME" IN ('<Connection Name>');
CommentAdd your comment...
Overview
Content Tools
search
attachments
weblink
advanced
I am migrating my on prem Jira server to Jira Cloud. The on prem server is connected to Jira Helpdesk Cloud right now. I would like to replicate the connection on Jira Cloud - Jira Helpdesk. How can I ensure that the issue types will map they way they were in Jira server-Jira Helpdesk Cloud? What is the risk to data loss with mapping and the new connection?
Is there going to be heavy script modification that I need to do to get the connection back up and running or simply copying the script from Jira on-prem to Jira Cloud do?