<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> Accurately capturing the incident start and end time is important because it allows teams to more accurately track metrics for ongoing efficiency reporting. Capturing these metrics also allows for potentially interesting analysis further down the line, such as a scatter plot of `impact start` by time of day, or avg response time by day of week. https://docs.gitlab.com/ee/operations/incident_management/incident_timeline_events.html#incident-tags  ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> As an incident responder, I want to capture relevant incident timestamps, so that I can construct an accurate incident timeline and provide reporting for learning and improvement. Right now, the only timestamps we capture for incidents are issue creation time or closure. Unfortunately, issue creation or closure may or may not correspond to the actual incident start or end time. Accurately capturing the incident start and end time is important because it allows teams to more accurately track metrics for ongoing efficiency reporting. Capturing these metrics also allows for potentially interesting analysis further down the line, such as a scatter plot of `impact start` by time of day, or avg response time by day of week. ### Intended users * Incident responders ### User experience goal <!-- What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>" https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ --> Ensure that the systems we're putting in place will result in accurate incident reporting ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> For a first iteration, we will allow incident responders to define the incident `start` and `end time`. Additional timestamp categories will be added in future, as part of https://gitlab.com/gitlab-org/gitlab/-/issues/360315. To allow users to define a tag, we'll utilize the existing "add timeline event" form, introducing a new "event type" dropdown. As a first pass, the options in this dropdown will include `start time` and `end time`. If someone selects a timestamp from the event type dropdown, the comment field will pre-populate with either `Incident start time` or `Incident end time`, depending on what's selected. That text can be edited by the user before saving. Here's how that would look: | New event tag field - default view | Help popover | Event tag options | Default event text supplied in the comment section | User may edit default comment text | Event tag indicated with badge on the timeline | Editing event tags | | ------ | ------ | ------ | ------ |------ | ------ | ------ | | |  | | |  | || [Figma file](https://www.figma.com/file/3k2HPBkWJPTTM90BAOe2cm/Capture-incident-timestamps-gitlab-com%26336026?node-id=1916%3A34069) ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> More discussion in https://gitlab.com/gitlab-org/gitlab/-/issues/241730#note_605624766 #### Vocabulary/definitions 1. Every timeline record is an `event` 1. An event may or may not have a `tag` (to differentiate from labels) 1. A tag is something with a specific definition that may be reused across incidents 1. There are GitLab defined `tags` - in the future, there may be customer defined `tags` and calculation based on custom tags. 1. A comment is a user provided input associated to an event 1. An event must have 1 comment. If a tag is selected we will pre-populate the comment field for users to edit. 1. An event can have 0 or more tags ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html * [ ] Add expected impact to members with no access (0) * [ ] Add expected impact to Guest (10) members * [ ] Add expected impact to Reporter (20) members * [ ] Add expected impact to Developer (30) members * [ ] Add expected impact to Maintainer (40) members * [ ] Add expected impact to Owner (50) members --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/workflow.html * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### Available Tier <!-- This section should be used for setting the appropriate tier that this feature will belong to. Pricing can be found here: https://about.gitlab.com/pricing/ * Free * Premium/Silver * Ultimate/Gold --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. Create tracking issue using the the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#three-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references <!-- Label reminders - you should have one of each of the following labels. Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->