[2B] Resolve Sentry error from error tracking list page
Problem to solve
Errors are noisy and plentiful which makes triage processes time-consuming because it is difficult to sort through the cruft to find the critical ones. By providing the ability to resolve an error in the GitLab UI, we give users another tool to clear out errors that have been fixed, allowing them to easily focus on the one's that require fixing.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
This work supports the Error Tracking Vision.
Proposal
Add the option to resolve Sentry errors in GitLab. It should be available in the list view for this iteration. Resolving an error should automatically close an associated issue.
Design
For the list page, we can change the ignore
icon button into a button group, and introduce the resolve
button. The button can utilize the existing check-circle icon.
Resolve error in list view |
---|
![]() |
- Resolving the error from this page would remove the error from the list view
- Ideally, the error would be hidden without a page refresh
- If an error is resolved from this view, any issues associated with it would also be automatically closed
- We should consider showing an informational alert letting users know that the associated issue has been closed:
The error has been resolved. The issue linked to that error has also been closed.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Amelia Bauerly