Skip to content

Commit 333a689

Browse files
Update docs/deliverables/2026-05-08-productbacklog/product-backlog.md
Co-authored-by: Manuel Lerchner <manuel.lerchner1111@gmail.com>
1 parent 3797754 commit 333a689

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/deliverables/2026-05-08-productbacklog/product-backlog.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
| Priority | User Story | Acceptance Criteria |
44
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
55
| 🔴 High | As an Incident Responder, I want to have all the relevant collected context regarding an incident, so that I dont have to search around and potentially loose information and time. | - Incident detail view shows description, status, assignments, timeline, comments<br>- Newly added information is reflected immediately |
6-
| 🔴 High | As a Incident Responder, I want to see a timeline of events for an incident so I understand what happened. | - Timeline displays all events in chronological order<br>- Events include type (status change, comment, assignment)<br>- Each event is timestamped |
6+
| 🔴 High | As an Incident Responder, I want to see a timeline of events for an incident so I understand what happened. | - Timeline is backed by an append-only incident event log (event-service)<br>- Timeline displays all events in chronological order<br>- Events include type (status change, comment, assignment)<br>- Each event is timestamped |
77
| 🔴 High | As an Incident Responder, I want to view a list of incidents so I can see active problems. | - Dashboard shows all incidents with key fields (title, status, severity, timestamp)<br>- Empty state shown when no incidents exist |
88
| 🔴 High | As an Incident Responder, I want to see the status of incidents so that I understand the urgency. | - Each incident displays its current status<br>- Status updates are immediately visible |
99
| 🔴 High | As an Incident Responder I want to create new incidents manually, so that incidents missed by the system don’t get lost. | - User can create incident with required fields (title, description)<br>- Validation prevents incomplete submissions<br>- Created incident appears in list |

0 commit comments

Comments
 (0)