Provide a mapping for Archived issues in the Jira integration like Resolved and Reopened

[al-the-x]

Problem Statement

We have the Jira integration configured to create Jira tickets when a Sentry Issue ramps up past a certain point. We also have it configured to close the Sentry Issue when the Jira ticket is closed and reopen existing Jira tickets when a closed Sentry Issue reopens.

There are some Sentry issues that are noisy and don't represent an error by themselves but a large surge in errors would be worth alerting the team about. We would like to use the Archive status in Sentry to silence them until they ramp or otherwise cross a threshold of activity. We don't want the Jira ticket to remain open indefinitely; we'd prefer the ticket to be closed and reopened when Sentry would reopen the Archived issue. Because of the Jira status mapping in the integration, when we close the Jira ticket, the Sentry issue is Resolved even if it WAS Archived and immediately reopens on the next error event.

We would like a way to Archive an issue in Sentry such that Sentry would allow the Jira ticket to be in a specific status AND move the Jira ticket into a mapped "Opened / Reopened" status when the issue crossed the Archive criteria, e.g. "For 10 users per day".

Solution Brainstorm

If Sentry had an additional Jira status mapping for Archived, we could mark the Sentry issue as "Archived" and move the ticket in Jira to our corresponding state (which we already use). When Sentry moved the issue back to "Open", the Jira issue would also move back to our mapped status.

Ideally we could do this all in one transition, but that's a little tricky, since Jira has no notion of the Archived criteria, and Sentry has no notion of what required fields are configured in Jira.

Product Area

Settings - Integrations

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[Dhrumil-Sentry]

This is a fair ask and tangentially related to #63615, Adding this to our backlog. We'll comment here once we have any updates