search checkboxes should default to just tickets

[jtm.moon.forum.user+trac@…]

Problem

Most of the time a user only wants to search tickets. However, the Search page defaults to checking all available checkboxes (Tickets Wiki Changesets etc.). The user must manually uncheck these for every search. This is annoying.

Solutions

There are few ways to improve this, in order of simplicity

1. tell users to remember the URL link i.e. https://trac/search?noquickjump=1&ticket=on
2. Global hardcoded default to auto-check only the Tickets checkbox.
3. Allow global Admininistration setting which allows picking which checkbox are auto-checked.
4. Allow per-user setting to allow picking which checkbox are auto-checked.

---

This is a follow-on to this ​old email thread.

I usually search with the search button, but 99% of the time, I only want to search tickets so it would be nice to default the other checkboxes to unchecked.

I'd like to have this feature too. I think it could be quite useful to store the search option on a per-user basis, so that the default search options are restored from one search session to the other.

[Ryan J Ollos]

Replying to jtm.moon.forum.user+trac@…:

Solutions

There are few ways to improve this, in order of simplicity

1. tell users to remember the URL link i.e. https://trac/search?noquickjump=1&ticket=on
2. Global hardcoded default to auto-check only the Tickets checkbox.
3. Allow global Admininistration setting which allows picking which checkbox are auto-checked.
4. Allow per-user setting to allow picking which checkbox are auto-checked.

The TracIni setting [search] default_disabled_filters allows disabling filters. See TracIni#search-section.

We could leave this ticket open for implementing a per-user preference. Another approach would be to have the state of the checkboxes persistent in the session data.

[jtm.moon.forum.user+trac@…]

Awesome, thanks rjollos .

The TracIni setting [search] default_disabled_filters allows disabling filters

This is a solution for option 2. I think that is good enough.

I think you could close this ticket as worksforme (I cannot close it).

[Ryan J Ollos]

Sounds good, I'll close as worksforme. I'm not convinced persistent session data would be a good approach. A user preference might be reasonable, but there are a number of other user preferences that should probably be implemented first, see comment:19:ticket:9807.

[Christian Boos]

Some users really insist on having their one way of using search remembered…

Hence this quick patch, 0001-search-save-last-selection-of-filters-in-the-session.patch​.

Ryan, as you expressed scepticism about this approach, I'm leaving the ticket closed. If you'd nevertheless be OK with the patch, let me know.

[Christian Boos]

store last selected search filters as comma-separated list in session, under key 'search.filters'

[Ryan J Ollos]

I think it would be okay to apply the patch. I don't have a strong preference either way, and it's easy to change the state of the filters, even if there are many, after #12376.

[Christian Boos]

Ok, thanks!

In branch cboos.git@t11292-save-search-filters-in-session.

[Christian Boos]

I've added a functional test for the feature and committed it as r15214.