[Frontend] Allow filtering issues search by status_name
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Supporting the work items custom status implementation for advanced search: &17575 (comment 2480612473)
The frontend must allow the user to filter work items by custom status
Proposal
The proposal is TBD but will likely involve the frontend sending an aggregations query to Elasticsearch to get the available custom statuses from the results and displaying those to the user in a drop down.
Questions
- There is some discussion about whether filtering would be allowed at global (no group or project selected) for GitLab.com. There may be a huge list of available filters at the global level on GitLab.com and I'm not sure it's performant enough to allow this. However, global search should be allowed for SM instances since there will likely be a much smaller set of custom statuses possible (even for larger SM instances
- How will the UX look? Specifically how will it look to allow selecting
inandnot in.
Edited by 🤖 GitLab Bot 🤖