Filter error list by release, merge request, commit
Problem to be solved
Sentry now supports GitLab for suspected commits, commit tracking, and releases like they do for GitHub. https://blog.sentry.io/2018/12/21/twelve-days-partners-gitlab
We should enhance the list view so you can filter based on these fields. We can follow a UX similar to Issues. This should also aligns nicely with our first-class Release concept (https://gitlab.com/gitlab-org/gitlab-ce/issues/41766), and we should enrich the list/commit views with links back to a pre-filtered list.
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
This work supports the Error Tracking Vision.
Provide three options to filter the Error list view, with a similar UX to our Issues list:
- By release
- By merge request (aggregating its commits)
- By commit (least valuable)
This list view can then serve as a foundation for expanding this data elsewhere into GitLab, namely our Releases, Merge Request, and Commit views.
For example when you are looking at a Release, we should show you how many errors were new in that release, as well as how many were closed. Similar with a Merge Request, it should show how many errors were traced back to commits that were a part of it.
|Default view||First dropdown options||Example second dropdown options||Example completed search field||Example recent searches dropdown|
Permissions and Security
Documentation required, most likely here.