🔧 chore(noa): invoke all ticketing actions via the issue alert handlers

[iamrajjoshi]

we need all of ticketing actions to flow to the issue alert handler.

this pr defines a new TicketingActionHandler ABC to handle invoking the issue alert handlers directly and updates the corresponding implementing classes to use the new ABC.

the changes are covered by this, so we should be good

[codecov]

Codecov Report

Attention: Patch coverage is 90.47619% with 2 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...low_engine/handlers/action/notification/handler.py	84.61%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #87372      +/-   ##
==========================================
+ Coverage   85.15%   87.76%   +2.60%     
==========================================
  Files        9875     9891      +16     
  Lines      559911   561363    +1452     
  Branches    22081    22081              
==========================================
+ Hits       476809   492694   +15885     
+ Misses      82697    68264   -14433     
  Partials      405      405              

[Copilot]

Pull Request Overview

This PR refactors ticketing actions by funneling them through the issue alert handler and introduces a new TicketingActionHandler abstract base class.

• Implements execute_via_metric_alert_handler to centralize notification handling for ticketing actions.
• Introduces TicketingActionHandler with a dedicated configuration schema for ticketing actions.
• Updates GitHub, GitHub Enterprise, Jira, Jira Server, and Azure Devops action handlers to extend TicketingActionHandler.

Comments suppressed due to low confidence (2)

src/sentry/workflow_engine/handlers/action/notification/handler.py:102

• [nitpick] The configuration schema for 'target_identifier' is defined as type ["null"]. Verify if this is intentional or if a more flexible type (e.g., ["string", "null"]) is expected.

"type": ["null"],

src/sentry/workflow_engine/handlers/action/notification/handler.py:109

• Ensure that ActionTarget is an iterable since using the splat operator (*) requires it to be unpackable.

"enum": [*ActionTarget],

[saponifi3d]

lgtm - but i think we should figure out a way to make execute_via_metric_alert_handler calling the issue alert registry a little less confusing.

[saponifi3d]

is there any data that should be included to ticketing actions by default?

[iamrajjoshi]

oop i forgot to add this, just did.

[saponifi3d]

This is a bit confusing -- metric_alert_handler calling into the IssueAlertRegistry 🤔 should this be via the issue_alert_handler?

[iamrajjoshi]

ope i used the wrong function name, it should be execute_via_issue_alert_handler