Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Link two issues to the same Jira ticket. Merge them.
- Go to the Jira ticket linked to both issues.
- Mark as
Done(the state matchingResolvedin Senry) - Sentry issue 93 (the "parent" issue of the merge) is marked as resolved.
- Wait some time
- The Jira ticket is reopened, as well as the Sentry issue 93, but issue has not presented itself in any new version.
https://dropbox.sentry.io/issues/4683300905/?project=4505546600087552
Expected Result
When ticket marked as done and ticket resolved in Jira, the ticket and matching Sentry issue should both remain resolved until a regression is seen.
Actual Result
The Jira ticket is reopened, as well as the Sentry issue 93, but issue has not presented itself in any new version.
Can't tell why the ticket is reopened in either Jira or Sentry, see #61878 for details of that issue.
My theory is that the merged issue (N2) is still affecting the Jira ticket, as I was seeing this behavior before I merged N2 into 93, but I cannot be sure it's still the reason. N2 would say it reopened the ticket, then 93 would reopen in response to the Jira ticket reopening.
See slack threads between DBX + Sentry:
https://dropbox.slack.com/archives/C04VDU7UZQE/p1704300001959139
https://sentry.slack.com/archives/C04VDU7UZQE/p1702678332601749?thread_ts=1702599116.070419&cid=C04VDU7UZQE
Product Area
Issues
Link
https://dropbox.sentry.io/issues/4683300905/?project=4505546600087552
DSN
No response
Version
No response
Metadata
Metadata
Assignees
Type
Projects
Status