feat(jira): control endpoint for fetching issue summaries

[cathteng]

For RTC-43

Implement a new Control-Silo endpoint for Jira to use which will perform region fanouts for issue data.

[codecov]

Codecov Report

❌ Patch coverage is 91.11111% with 4 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...ry/integrations/jira/views/sentry_issue_details.py	90.69%	4 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #98324    +/-   ##
========================================
  Coverage   81.17%   81.18%            
========================================
  Files        8536     8537     +1     
  Lines      376194   376322   +128     
  Branches    23922    23922            
========================================
+ Hits       305374   305507   +133     
+ Misses      70454    70449     -5     
  Partials      366      366            

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[seer-by-sentry]

Potential bug: The region fanout loop in JiraSentryIssueDetailsControlView lacks error handling for RPC calls, causing the entire request to crash if any single region is unavailable or times out.

• Description: The JiraSentryIssueDetailsControlView iterates through all regions to fetch linked Sentry issues using the issue_service.get_external_issue_groups() RPC call. This call can raise exceptions like RpcRemoteException, ConnectionError, or Timeout if a region is unavailable or experiences network issues. The loop at src/sentry/integrations/jira/views/sentry_issue_details.py:236~242 does not have a try/except block to handle these potential failures. As a result, an issue in any single region will cause the entire endpoint to fail with an unhandled exception, leading to a 500 error for the user instead of showing partial results from available regions.

• Suggested fix: Wrap the issue_service.get_external_issue_groups() call inside the for loop with a try/except block. Catch relevant exceptions, such as RpcRemoteException, and log the error while allowing the loop to continue to the next region. This will make the endpoint more resilient to partial region failures.
  _{severity: 0.81, confidence: 0.95}

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[leeandher]

Approving since it all looks good! Just the one comment I think should be addressed but its a quick fix, great work 👏

[leeandher]

Rather than fanout to every region, we can filter to regions with an associated installation, this is what the parsers do.

Take a look at find_regions_for_orgs, and you can get the org_ids from something like:

organization_integrations = OrganizationIntegration.objects.filter(
  integration_id=integration.id,
  status=ObjectStatus.ACTIVE,
)
organization_ids = [oi.organization_id for oi in organization_integrations]

[cathteng]

Done! Thanks for the suggestion!

[cursor]

Bug: Mock Ineffectiveness in Jira Issue Hook Test

The test_simple_get in JiraIssueHookControlTest mocks ExternalIssue.objects.get, but the JiraSentryIssueDetailsControlView uses issue_service.get_external_issue_groups(). This makes the mock ineffective for testing the control view's behavior. The mock's side effect also assumes a specific region processing order, which could lead to flakiness.