You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1143: Add multi-selection to issues search (eg. "show open AND new bugs" etc)

Kind feature request
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

So we already have "inclusion" filtering in the form of clicking on "Open", "Closed", "New" status links, or product names etc. This causes us to include only issues which belong to a particular category.

But often I find myself wanting to do "exclusion" filtering, in the sense of "show me all issues except for ones which match this category". A common example would be "show me all issues except for closed ones".

There are two ways I could implement this:

  1. In the search interface convert the pop-up menus into multi-section lists
  2. Or add checkboxes or similar above the table (perhaps hidden inside a "filter" div) which would allow the user to exclude a certain category; if I took this path I would most likely start with the obvious candidates for exclusion only, "closed" issues.

Comments

  1. Greg Hurrell

    On thinking about this more (ie. for almost 2.5 years), I like the first solution better.

    The idea would be to have the existing pop-ups, but add a checkbox to the side that would be labelled something like "select multiple"; on marking it, the pop-up would expand out to a multi-selection list. Will update the summary accordingly.

  2. Greg Hurrell

    Summary changed:

    • From: Add (exclusion) filtering to issue tracker
    • To: Searcg issue tracker
  3. Greg Hurrell

    Summary changed:

    • From: Searcg issue tracker
    • To: Add multi-selection to issues search (eg. "show open AND new bugs" etc)
  4. Greg Hurrell

    On thinking about it for a few more years, I think this is the wrong feature. The distinction between "new" and "open" is pretty useless, and I think nobody really cares about it, not even me. The original intention was for "new" to mean "untriaged", and "open" was to mean "accepted as valid, but not yet finished".

    If I just collapse "new" and "open" into one category ("open"), the major motivating use case for this feature request is simplified out of existence. I can imagine still wanting some form of this in the future, but right now, I don't think I need it (and to be honest, implementing it on this old Rails stack sounds a bit painful anyway, so I'm happy to defer it).

    Closing.

  5. Greg Hurrell

    Status changed:

    • From: open
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu