### Release notes ### Problem Incident timelines are an important part of record keeping for incidents. They give a high-level overview, to executives and external viewers, of what happened during the incident, and the steps that were taken for it to be resolved. The current process for creating incident timelines (adding a list of what happened/when in the incident description, often after the incident ends) is a manual and time-consuming process. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager) * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) * [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor) --> * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Metrics <!-- How are you going to track uage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> [Metrics & Instrumentation for Incident Timelines](https://gitlab.com/gitlab-org/gitlab/-/issues/345187) ### Original vision designs Goal: Allow people to easily create an editable timeline on incidents. | Add timeline tab + way to easily add comment items to timeline | Timeline view | Allow for adding/sorting of timeline view | Timeline actions (starring, editing, deleting) | Timeline editing close-up | | ------ | ------ | ------ | ------ | ------ | | | |  || | Original [vision design figma file](https://www.figma.com/file/tWk48ndpYzMOgs4jH5t4zj/Monitor-vision-Monitor-and-41?node-id=559%3A5185) ### Validated High Fidelity Mock-Ups | Add timeline tab + way to easily add comment items to timeline | Tooltip | Toast | Timeline view | Timeline menu items | In-line editing | Add new item to timeline | New item added to timeline | Slash command | | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ | | | |  |  | | | |  |  | | Mobile | Mobile actions menu | Edit | | ------ | ------ | ------ | |  | | | Figma file for [timelines](https://www.figma.com/file/01efUzilO8y3FZndx4Kt14/Incident-timelines-gitlab-com-and-330901?node-id=63%3A342) **Additional details** - Timeline items will automatically be ordered by time/date. Dates are currently shown in UTC, as that's what our SRE team requires. But, many co-located teams will likely just want their timelines displayed in their local times. So, in future, we'll need to figure out how to make the timezone customizable (or to change the display to a local time, if/as needed). - We'll need to carefully consider permissions for timelines. Probably only higher permission levels (Developer and up) should have the option to edit or delete the timeline. For everyone else, it should be view-only. - When the timeline is edited, we'll need a record of what was changed, by whom. We can use the normal system notes on the issue summary tab to support this:  - We'll likely want to have new timeline items trigger notifications, just as new comments do on issues. - The design specifies that we will automatically add some system notes to the timeline. But, we may need some additional discussion to clarify _which_ system notes will be included, and which excluded. - Longer-term, we'll want people to be able to add/edit simultaneously. We'll likely need additional technical investigation to see if this will be possible for the MVC, or if we need to have a less complicated version of this functionality for a first pass. - Since we're introducing a second "edit" functionality on incidents, we should ensure the existing "edit" button (which only impacts the summary tab) is hidden when people switch to any other tabs. - The [slash command](https://gitlab.com/groups/gitlab-org/-/uploads/e2156453ad4a19ceeeb35c9cf37c49ae/Slash_command.png) is a nice-to-have addition, but not required for the MVC. - When we build this, we'll need to reconsider the naming of our older "timeline view" functionality. We should, at the very least, update the "timeline view" tooltip when this new timeline is introduced:  ### Release Notes To be filled