<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ### Problem to be solved Errors are often plentiful, noisy, and challenging to dig through to find the important ones that are impacting users. As we are displaying a list view of Sentry errors in GitLab, we need to provide users with tools (such as search, sort, and filter) to refine this list according to criteria that is important to them. 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. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Further details This work supports the [Error Tracking Vision](https://about.gitlab.com/direction/monitor/debugging_and_health/error_tracking/). ### Proposal 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. ### WIP Design | Default view | First dropdown options | Example second dropdown options | Example completed search field | Example recent searches dropdown | | ------ | ------ | ------ |------ |------ | |  |  |  |  |  | ### Permissions and Security ### Documentation Documentation required, most likely [here](https://docs.gitlab.com/ee/user/project/operations/error_tracking.html#error-tracking-list). ### Testing ### What does success look like, and how can we measure that? ### What is the type of buyer? ### Links / references