Custom query does not allow to search for "resolution=none"

[Peik Aschan <peik.aschan@…>]

My use case is as follows: We are starting the test phase of a release of our product, and for our test plan, I need to get a list of all tickets that will really be included in the release, excluding those that have been marked as invalid, duplicate or wontfix/cantfix.

The query can be performed with the following URL:

​http://trac.edgewall.org/query?milestone=0.12&resolution=!invalid&resolution=!duplicate&resolution=!wontfix&resolution=!cantfix

But this query is not possible to construct with the query UI, instead I have to enter the URL manually. At this stage, I still have a lot of tickets open and with no resolution, which will be filtered out if I select the resolutions fixed and worksforme in the UI.

If you were to add an option for "resolution=none" to the resolution search criteria, this would solve my problem.

Way to reproduce: enter the above URL into the browser, take note of the ticket count, then press Update. Notice how the ticket count decreases as the unresolved tickets are filtered out.

[Remy Blank]

Here on t.e.o, the tickets that will be included are those that are resolved as "fixed", so the query you describe would be:

​http://trac.edgewall.org/query?milestone=0.12&resolution=fixed

If you want to include tickets that have no resolution, you should additionally check the status (only closed tickets have a resolution). Or clauses can help you with that:

​http://trac.edgewall.org/query?milestone=0.12&resolution=fixed&or&milestone=0.12&status=!closed

And that query is editable on the query interface. Would that work for you?

[Peik Aschan <peik.aschan@…>]

Thanks, you are right, the second query does work for my use case. I didn't even consider the OR clause, since this feature is new to 0.12, which we are not yet using.

However, I would still argue that it would make sense to allow searching for "resolution=none", since "none" (or actually null) really is a valid value, and this would allow simpler queries. But if this is not reasonably easy to implement, I don't mind you closing this ticket as wontfix.

[Remy Blank]

Thanks for the feedback. It is certainly possible to add a "<none>" option to checkbox fields, and I would probably integrate a patch implementing this. I'm not too motivated to implement it myself, though, considering there's an alternative solution.

So I'm assigning this to 1.0 until someone submits a patch.

[Christian Boos]

Milestone 1.0 deleted

[Remy Blank]

Let's close this, as the functionality is already available (comment:2).