JIRA Integration Breaks When Issues Move Between Projects #101334
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
The Sentry-JIRA integration stores the JIRA issue key (e.g., "TDP-22") in the annotations field of Sentry issue. When a JIRA ticket is moved to a different project, the key changes (e.g., to "NEWPROJ-123"), breaking the connection between Sentry and JIRA.
Expected Behavior:
The integration should store Sentry Issue ID as a JIRA ticket property not the other way round (as it is right now).
Current Workaround:
None - users must manually re-link Sentry issues to the moved JIRA ticket.
Impact:
Medium-High - Common workflow in enterprise environments where tickets are triaged in one project and moved to team-specific projects.
Expected Result
The integration should store Sentry Issue ID as a JIRA ticket property not the other way round (as it is right now).
Actual Result
Users must manually re-link Sentry issues to the moved JIRA ticket.
Product Area
Issues
Link
No response
DSN
No response
Version
No response