Empty search results vs empty filter results empty state text guidance
Description
We added some documentation around empty search results recently in #1210 (closed). When I used them for gitlab-org/gitlab#339525[Deleted-many-items.png] (comment 820337312), they didn't quite fit since there were filters applied. There are cases when something is searched within a search input field that will result in no matches, as well as when something is filtered within the filter component that can also result in no matches. We should decide whether or not we want to provide different messaging for those.
Audit of empty state cases
Summary |
---|
Whether we use a search component to filter down results, or the filter component, we do not consistently provide messages as to why there were no matches. |
7/17
instances use something similar to the following text:
Sorry, your filter produced no results
To widen your search, change or remove filters above
only 3/10
instances use something similar to the following text:
Sorry, no projects matched your search
Full audit table
Proposal
Search
If a page uses the search component, use the following text for empty states:
No results found
Edit your search and try again.
Filter
If a page uses the filter component, use the following text for empty states:
No results found
Edit your filters and try again.
Checklist
Make sure the following are completed before closing the issue:
-
Assign the correct component label to this issue. -
Create an MR with the additions or updates needed. !2751 (closed) -
When applicable, create a new Pajamas issue using the "Figma update" issue template to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When applicable, create an MR in GitLab UI to update the component. If you do not have capacity or are unable to update the component directly, create a new GitLab UI issue using the "Component" issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting. -
🎉 Congrats, you made it! You can now close this issue.