Migrating Jira cloud to Cloud, need support for Sentry Integration

[JagSid]

Environment

SaaS (https://sentry.io/)

What are you trying to accomplish?

Hi Team,

we have a client who uses sentry currently integrated with their source Jira. They are migrating to another Jira cloud instance. What is the migration path for Sentry, will it re-connect to tickets automatically or do we need to do some manual mapping?

How are you getting stuck?

no clear migration path

Where in the product are you?

Settings - Integrations

Link

No response

DSN

No response

Version

No response

[getsantry]

Auto-routing to @getsentry/product-owners-settings-integrations for triage ⏲️

[sentaur-athena]

Actually not sure about this but taking a quick look it doesn't seem like there exists a nice migration path. The Jira cloud instance requires new installation and a new configuration 🤔 And alerts are mapped to the configuration so to me it seems like it would require re-doing everything.

[JagSid]

Hi Athena, Thank you for confirming I will let the client know. Is there a way to pull or re-establish links between tickets. Or how does the linking work, seeing if we can do some manual re-mapping.

…

________________________________ From: Athena Moghaddam ***@***.***> Sent: Thursday, February 20, 2025 1:19 PM To: getsentry/sentry ***@***.***> Cc: Jagpal Sidhu ***@***.***>; Author ***@***.***> Subject: Re: [getsentry/sentry] Migrating Jira cloud to Cloud, need support for Sentry Integration (Issue #85535) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> External Actually not sure about this but taking a quick look it doesn't seem like there exists a nice migration path. The Jira cloud instance requires new installation and a new configuration 🤔 And alerts are mapped to the configuration so to me it seems like it would require re-doing everything. — Reply to this email directly, view it on GitHub<#85535 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPWVAXFRXPEKIFHREEUL46L2QYMEXAVCNFSM6AAAAABXRAFINKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGMYTQNJYGA>. You are receiving this because you authored the thread.Message ID: ***@***.***> [sentaur-athena]sentaur-athena left a comment (getsentry/sentry#85535)<#85535 (comment)> Actually not sure about this but taking a quick look it doesn't seem like there exists a nice migration path. The Jira cloud instance requires new installation and a new configuration 🤔 And alerts are mapped to the configuration so to me it seems like it would require re-doing everything. — Reply to this email directly, view it on GitHub<#85535 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPWVAXFRXPEKIFHREEUL46L2QYMEXAVCNFSM6AAAAABXRAFINKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGMYTQNJYGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[sentaur-athena]

@JagSid unfortunately there's no easy way because external issues (Jira tickets) would have different IDs when Jira Cloud changes. But you can write a script to make this a bit less painful.

1. Install another Jira integration on the org so there are basically 2 configurations for Jira
2. You can then get all the issues linked to integrations using GroupIntegrationEndpoint. This endpoint is not publicly documented which is why I'm sending you the code.
3. Now that you have issues and integration IDs for each issue you need to make a PUT request to GroupIntegrationDetailsEndpoint with the issue in mind and the new integration ID to create a Jira ticket for it on the new Jira cloud.

PUT https://us.sentry.io/api/0/organizations/{org-slug}/issues/{issue_id}/integrations/{the_new_integration_id}/

[JagSid]

is the integration ID the jira issue key?