Ticket Search should (optionally) search only non-closed tickets

[Norbert Unterberg <nepo@…>]

One of the popular uses for searching (I believe) is to search the ticket database if an issue has already been filed. It would help if the search would only search tickets that have not been closed.

This request is similar to Ticket #584 but I would like a way to filter the results so that only open tickets are displayed in the search result. It does not help much if you need to browse loads of resolved tickets to find the one open ticket you are looking for.

fixed typos

[dneary@…]

This is a part of ticket #1722 (since closed as invalid).

It would be nice if someone could outline how this could be done - I did look at the template code, but couldn't figure out an easy way to filter on the bug's status. I would be prepared to make the change, if I had some idea how to go about it.

[Christian Boos]

My current take on the issue is that there should be a way to "forward" the list of tickets found during a search to the custom query view, where one can add additional criterions to refine the search or better organize the results.

Alternatively, a "free text form search" could be reintroduced on the custom query page.

See related discussion on ​TracDev:333

[Christian Boos]

#6869 was closed as duplicate.

[Christian Boos]

#7900 was closed as duplicate.

[anonymous]

Any news on that issue? It's really, really boring having not the capability to do this

[Christian Boos]

The possibility to forward results to a custom query view (comment:2) was implemented in a branch, this should eventually be revived for (one of the) next major version. See SearchRefactoring#Reuseofresults1.

[Ryan J Ollos <ryano@…>]

I have exactly the same issue as the reporter of this ticket, which is what led me here. It seems like it would be worthwhile to implement open and closed checkboxes in the interm, even if its not the best long term solution.

This seems like a reasonable sized ticket that I'd be willing to tackle, though the fact that its been open so long makes me wonder if it is more challenging than I anticipate.

[Ryan J Ollos <ryano@…>]

Not sure if there is any potential overlap, but #9098 is a feature request for individual Tickets open and closed filters on the timeline.

[Remy Blank]

I intended to implement the "throw tickets from a search result list into a ticket query" functionality in #3375, which is actually a duplicate of this ticket. So I'd rather not add a "temporary" solution at this point.

[Remy Blank]

#10031 was closed as a duplicate.

[tony.meyer@…]

Alternatively, if the custom query interface allowed a search term as a filter, any number of variations of this would be possible (e.g. open in open tickets, only in closed tickets, only in tickets belonging to X, only in tickets that are in this milestone and open, …).

[anonymous]

6 years and still there isn't a simple check box to filter open/closed tickets. Obviously the whole search is useless as it is now and needs refactoring but at least this very simple feature will help a lot of people.

[tony@…]

Replying to tony.meyer@…:

Alternatively, if the custom query interface allowed a search term as a filter, any number of variations of this would be possible (e.g. open in open tickets, only in closed tickets, only in tickets belonging to X, only in tickets that are in this milestone and open, …).

Sigh. Somehow I missed that this was already possible. So IMO there's not a great need for this, because it's far better to do a custom query for open tickets with a description/summary term - in fact, a "search" for tickets is almost always the wrong thing to do, and a custom query the right thing (searching is for wiki/changeset/milestone).

[axeld]

Good luck telling this the average user :-)

[anonymous]

a simple user maybe doesn't have access to the custom query. the general search is generally the only tool available for him.

[Ryan J Ollos]

Retargetting tickets to narrow focus for milestone:1.2. Please move the ticket back to milestone:next-dev-1.1.x if you intend to resolve it by milestone:1.2.