| Reporter |
Paul Shmakov (Paul.Shmakov)
|
|---|---|
| Created | May 15, 2013 2:48:40 PM |
| Updated | May 20, 2013 3:52:00 PM |
I found a usability issue with the "Clear search input" button (shown as "X" in a search box). It just clears the text, but does not refresh the search results. One has to explicitly click on a Search button to apply the new filter. And this is confusing. Especially when you switch to another tab, for example, from "Issues" to "Agile Board" - recently cleared search input appears again and is effective on a new tab.
It isn't consistent with other UI elements - when one clicks on a saved search, it applies immediately.
What steps will reproduce the problem?
1. On the Issues page apply some search filter. For example, "commenter: me".
2. Click on "Clear search input" button.
3. Click on "Agile Board".
4. Check the search box.
What is the expected result?
The search box is empty and the agile board shows all issues without any filtering applied.
What happens instead?
The search box contains "commenter: me" and the agile board shows a subset of issues.
It isn't consistent with other UI elements - when one clicks on a saved search, it applies immediately.
What steps will reproduce the problem?
1. On the Issues page apply some search filter. For example, "commenter: me".
2. Click on "Clear search input" button.
3. Click on "Agile Board".
4. Check the search box.
What is the expected result?
The search box is empty and the agile board shows all issues without any filtering applied.
What happens instead?
The search box contains "commenter: me" and the agile board shows a subset of issues.