Hello, On Fri, Sep 02, 2022 at 04:23:49PM -0500, G. Branden Robinson wrote: ... > Then, I click open the "Display Criteria" widget, and change the "Browse > with the" list box control from "Basic" to "Enhanced", because I want to > filter items by "Planned Release", and even the "Advanced" query > interface doesn't enable that. I then click the "Apply" button to > submit the form. ...
Tracker admins can add custom query types for their tracker. "Enhanced" in groff bug tracker is such custom query; it includes "Closed on" both as an output column and as a selection criterion... [reordered] > 5. Even if I change the operators from "greater than" to "less than", I > _still_ get no results. This is because the "Open/Closed" control is > still on "Open", and the "close_date_op" filter is still applied. ... ...and when a date field is undefined, it matches no range [0], so it makes the query unsuitable for browsing items that have never been closed. [0] https://git.savannah.nongnu.org/cgit/administration/savane.git/tree/frontend/php/include/trackers_run/browse.php?id=8fefb52bdf34a501c56cb403dd225b665050aa4a#n443 > 1. Once the "Enhanced" form has been presented, there's no way via the > controls on the page to omit them. The filter always applies. Correct; this is why various query types exist. > 2. The dates always default to the current date and the _greater than_ > operator. This is guaranteed to fail. No bugs are ever submitted or > closed in the future. Good point. > 3. There's no option in the controls to disable these two filters. Strictly speaking, there is---for tracker's admins when defining the query type. > 6. To really use the filtering-by-date feature, you have to edit the URL > by hand. This is tedious. > > 7. Erasing the operator from the chunk of the HTTP GET query doesn't > work, possibly because there's no empty or null option for the date > ordering operator. It defaults to the first item in the list, which > is "<". (This appears to be true for both "date_op" and > "close_date_op".) You have to remove these chunks entirely. I don't understand how these are possible.
signature.asc
Description: PGP signature