-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
-
Goal
- Track engineer / SRE contributors to incidents
Why is this important?
- To be able to tell who was actively involved in the incident resolution without having to either:
-
- Be present in the web-rca bridge for the whole duration of the incident
- Scour the incident slack channel for people contributing to the root causing and/or solution
- Track all the associated Jira links in the incident
- Go around asking the participating people
- The current fields only represent who is currently on the role and provide very little insight that is useful in retrospective action
- To be able to go back and find the correct stakeholders who might be able to provide additional detail to the incident should a similar occur.
Scenarios
- In the incident detail, I want to see who has been involved in the active troubleshooting, identification of impact and solution coding.
- In the incident search I want to be able to find the incidents a Red Hat employee contributed to
Acceptance Criteria
- RCA details has a new "Contributors" field that is a list of Red Hat employees that have actively participated in the solution
- A new filter in the search exists to find all the incidents in which somebody is involved.
Dependencies (internal and external)
- Red Hat employee ids
Out of scope:
- Automating populating contributors from filed issues. We can leave that as a future Epic
- account is impacted by
-
RHCLOUD-40211 WebRCA: Validation of redhat employee id for Contributors field
-
- Backlog
-
-
RHCLOUD-40212 WebRCA: Automating populating contributors from filed issues
-
- Backlog
-