Skip to content
ari edited this page Dec 26, 2011 · 4 revisions

The task filter is a powerful and quick to use interface to search on tasks. We need to unify searching concepts throughout:

  • users
  • clients
  • resources (this is especially bad now)
  • timeline
  • reports
  • projects (maybe)

Where is the filter?

  • In the right column (like task) or in the top of each page.
  • Do we need height or width?
  • Should it appear as part of the page or part of the navigation/layout?

Do filters persist?

Task filters stick when you navigate away and come back. Do others?

Are all filters implemented like the task filter (free text entry) or are others more ’guided" with checkboxes and menus

Interesting ideas here: http://youtrack.jetbrains.net/ and here http://www.jetbrains.com/youtrack/features/search_filter_issues.html They have managed a nice combination of both. Some parts of jobsworth could do with the GUI approach. For example, the existing reports filter: a checkbox to disable worklogs already exported is helpful. Or a checkbox to hide all closed tasks.

Youtrack solves this by showing a faceted search filter list (as checkboxes) once you perform a search. This idea is nice, but takes up lots of space.

Do other entities have saved filters or only tasks?

What is the relationship between filters?

If you are looking at the client “Acme” is there an easy way to then look at tasks filters for that client?

Unified search

Should the user navigate to the right page first (eg. /users) and then perform a search, or do they switch the mode of a generic search UI to make it return different results and display the right page (faster to use, more complex UI)

Should filters be on every page?

If filters display on irrelevant pages, what should be done when user clicks one filter? Navigate to a new page, or load results through ajax and display on current page?