Content
View differences
Updated by Wieland Lindenthal almost 2 years ago
### Steps to reproduce
* Open the work packages page
* Type something in "Search" in the sidebar
* Don't find what you are searching for, because it will only search the saved filters on work packages in the sidebar
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/114168/content">
### What is the buggy behavior?
* You actually need to open the "Filters" to do a search in the text of a work package. Since they are called filters, not search, it's unexpected that to you have to open that for a text search (at least for me 😉 ) .
### What is the expected behavior?
* The "search" could maybe search for both (then the results would have to be structured, e.g. first list matching saved filters, then work packages or maybe filter the sidebar and list text-search-results in the content area in the right)
* Or let the user decide what to search for, like e.g. GitHub does: <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/114169/content"> Maybe there is even another, better way to solve this UX wise.
* Open the work packages page
* Type something in "Search" in the sidebar
* Don't find what you are searching for, because it will only search the saved filters on work packages in the sidebar
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/114168/content">
### What is the buggy behavior?
* You actually need to open the "Filters" to do a search in the text of a work package. Since they are called filters, not search, it's unexpected that
### What is the expected behavior?
* The "search" could maybe search for both (then the results would have to be structured, e.g. first list matching saved filters, then work packages or maybe filter the sidebar and list text-search-results in the content area in the right)
* Or let the user decide what to search for, like e.g. GitHub does: <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/114169/content"> Maybe there is even another, better way to solve this UX wise.