Saved searches/filters for issues
Description including problem, use cases, benefits, and/or goals
It’s common for teams with large number of issues to want to see specific lists, such as:
- issues with label “blocker” and milestone “version 1.0”
- issues with milestone “version 1.0” and no assignee
These searches are easy to perform using GitLab issues, but they have to be repeated every time. There is also not an easy way to share them among team members. That’s why saved searches are a part of most advanced issue trackers.
Saved searches enables teams to customize GitLab’s issue list to what they need for their workflows.
When viewing a custom search/filter result, a “save” button could appear that allows for saving current view with a name. Saved searches can appear right after “Open,” “Closed,” and “All.” Clicking on their name applies the same search/filters.
The option used for ordering the issues could be a part of the saved views as well.
Links / references
- Please note that this is different from what is discussed at #17907 (closed). Issue boards, which are great, work around states (using labels) and that is only one criteria that can be used for searching.