102 lines
3.6 KiB
Markdown
102 lines
3.6 KiB
Markdown
---
|
|
stage: Monitor
|
|
group: Respond
|
|
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
|
---
|
|
|
|
# Timeline events
|
|
|
|
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/344059) in GitLab 15.2 [with a flag](../../administration/feature_flags.md) named `incident_timeline`. Enabled by default.
|
|
> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/353426) in GitLab 15.3.
|
|
> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/353426) in GitLab 15.5. [Feature flag 'incident_timeline'](https://gitlab.com/gitlab-org/gitlab/-/issues/343386) removed.
|
|
|
|
Incident timelines are an important part of record keeping for incidents.
|
|
Timelines can show executives and external viewers what happened during an incident,
|
|
and which steps were taken for it to be resolved.
|
|
|
|
## View the timeline
|
|
|
|
Incident timeline events are listed in ascending order of the date and time.
|
|
They are grouped with dates and are listed in ascending order of the time when they occurred:
|
|
|
|
![Incident timeline events list](img/timeline_events_v15_1.png)
|
|
|
|
To view the event timeline of an incident:
|
|
|
|
1. On the top bar, select **Main menu > Projects** and find your project.
|
|
1. On the left sidebar, select **Monitor > Incidents**.
|
|
1. Select an incident.
|
|
1. Select the **Timeline** tab.
|
|
|
|
## Create an event
|
|
|
|
You can create a timeline event in many ways in GitLab.
|
|
|
|
### Using the form
|
|
|
|
Create a timeline event manually using the form.
|
|
|
|
Prerequisites:
|
|
|
|
- You must have at least the Developer role for the project.
|
|
|
|
To create a timeline event:
|
|
|
|
1. On the top bar, select **Main menu > Projects** and find your project.
|
|
1. On the left sidebar, select **Monitor > Incidents**.
|
|
1. Select an incident.
|
|
1. Select the **Timeline** tab.
|
|
1. Select **Add new timeline event**.
|
|
1. Complete the required fields.
|
|
1. Select **Save** or **Save and add another event**.
|
|
|
|
### Using a quick action
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368721) in GitLab 15.4.
|
|
|
|
You can create a timeline event using the `/timeline` [quick action](../../user/project/quick_actions.md).
|
|
|
|
### From a comment on the incident
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/344058) in GitLab 15.4.
|
|
|
|
Prerequisites:
|
|
|
|
- You must have at least the Developer role for the project.
|
|
|
|
To create a timeline event from a comment on the incident:
|
|
|
|
1. On the top bar, select **Main menu > Projects** and find your project.
|
|
1. On the left sidebar, select **Monitor > Incidents**.
|
|
1. Select an incident.
|
|
1. Create a comment or choose an existing comment.
|
|
1. On the comment you want to add, select **Add comment to incident timeline** (**{clock}**).
|
|
|
|
The comment is shown on the incident timeline as a timeline event.
|
|
|
|
### When incident severity changes
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/375280) in GitLab 15.6.
|
|
|
|
A new timeline event is created when someone [changes the severity](incidents.md#change-severity)
|
|
of an incident.
|
|
|
|
![Incident timeline event for severity change](img/timeline_event_for_severity_change_v15_6.png)
|
|
|
|
## Delete an event
|
|
|
|
You can also delete timeline events.
|
|
|
|
Prerequisites:
|
|
|
|
- You must have at least the Developer role for the project.
|
|
|
|
To delete a timeline event:
|
|
|
|
1. On the top bar, select **Main menu > Projects** and find your project.
|
|
1. On the left sidebar, select **Monitor > Incidents**.
|
|
1. Select an incident.
|
|
1. Select the **Timeline** tab.
|
|
1. On the right of a timeline event, select **More actions** (**{ellipsis_v}**) and then select **Delete**.
|
|
1. To confirm, select **Delete Event**.
|