Annotate status changes on alerts
Problem to solve
When teams are triaging alerts, they need a way to annotate changes in status so that team members know why the status was changed and if any followups are needed. Annotations will help to share context broadly among team members which will reduce confusion and the need to constantly update team members synchronously.
Intended users
Further details
This work drives the direction of the Alert Management category.
Proposal
Following what's been done on vulnerabilities, we can have a commenting section appear as part of the system notes when the status is changed:
Status is changed - comment field appears | Field is activated | Text is added | Final state with additional system note |
---|---|---|---|
A new note field will appear each time the status is changed. Any edits to the note field can be captured in the system notes.
Update: we've recently decided to move the system notes to a separate tab. Depending on the order of implementation, the location of these annotations might change from what's shown in the designs above. When the system notes move to a separate tab, the annotations will, as well.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.