[Workflow Notification] Incorporate the event_id that caused the regression into the Issue URL #103939
Description
Problem Statement
Workflow notifications for issue regressions do not link to the event that caused the regression but rather the issue more generally.
Solution Brainstorm
The event_id is already captured and stored in the regression activity data, and the URL generation infrastructure already supports linking to specific events. We'd need to modify RegressionActivityNotification class to pass the event_id from self.activity.data to the get_absolute_url() method.
It would likely be good to also show the stack trace from the event that caused the regression, not from the first event on the issue (as is currently the case).
Product Area
Issues