As part of the TRT-336 epic we plan to restore Jira support in sippy, detecting links between Jiras and tests/jobs, and storing that data in our db.

We should investigate if it would be possible to tie this into our alerting system. Sippy should alert us when there's a problem with a job or test, in some capcity. If we were to then file a Jira, label it an incident, link it to as many releated tests/jobs as possible, we could potentially use this to:

• snapshot pass rates prior to the incident, during the incident, and after the incident
• analyze how we did
• automatically notify when pass rates dip back into the range of past incidents
• record severity of CI incidents and report
• display a history of incidents related to a test or job in the UI
• display an on-going incident to anyone browsing the UI
• silence the alerts as soon as the incident is opened
• consider the incident closed when the jira is closed
• eliminate the need for authentication in the sippy UI (for now) by using an indicrect mechanism to comment on jobs/tests and their history
• find a way to categorize incidents: cloud outage, code revert, unknown