Feature Request: Jira ticket linkage to apply resolution strategy

Problem Statement

Broad description of the ask

Currently when you mark a ticket as done, it pings Sentry that the issue is fixed in the current version, which is not true and results in the issue "regressing".

Manually marking the issue as fixed or fixed in the next release is also available, but does not allow one to mark as fixed in a future release(other than 'next').

Solution Brainstorm

I would like Jira issues to report back to Sentry when an issue has been marked as done, specifically which "FixVersion" we expect to have that fix. Jira will ping sentry (potentially)

Jira would send additional information to Sentry, and Sentry would use that info to set an anticipated release version target for issue resolution:

https://sentry.io/api/0/organizations/etsy/releases/ with "issue.fixVersions.name"
Custom Data set up:

{
  "version": "com.FOO{{issue.platform.name}}@{{issue.fixVersions.name}}",
  "projects": ["{{issue.platform.name}}"]
}

Here is an example workflow:

1. A new issue called "NewError" is caught in Sentry in App Version 1.1.
2. User creates a Jira ticket - lets call it "MyIssue-200" from the Sentry UI for that issue.
3. User goes to Jira and finds the "MyIssue-200" Jira ticket.
4. They make a change to the code and schedule that change for App Version 1.2 which will be released in 1 week
5. They update the ticket with FixVersion: 1.2 and then mark the ticket as Done
6. The automation should ping Sentry(see above), alerting Sentry that the issue named "NewError" will be resolved in App Version 1.2

Product Area

Issues

Start by reviewing the Jira workflow described in the issue and the Sentry releases API at https://sentry.io/api/0/organizations/etsy/releases/. Trace how Jira FixVersion data could reach Sentry when an issue is marked Done, and clarify the integration entry points and expected behavior before implementing. Done means a completed Jira issue communicates its anticipated release without causing a premature regression.