Peter Suter <[email protected]> writes: > On 16.09.2015 14:04, Greg Troxel wrote: >> I have long noticed that when doing a custom ticket query that even if >> asking for open tickets (which seems the normal case), tickets that were >> closed in the last hour or so show up. >> >> I can see why people would want this at times, but it seems plainly >> wrong given the ticket query string. It's also highly unhelpful when >> going through and cleaning up tickets that should have been closed long >> ago, because the ones that have been dealt with do not disappear from >> the query. >> >> Should there be an option to include tickets that recently met the >> search criterea? > I don't think there's any intended special behavior for recently > closed tickets. But there is a feature[1] that can maybe be > misinterpreted that way: > >> When you return to the query any tickets which were edited will be > displayed with italicized text. If one of the tickets was edited such > that it no longer matches the query criteria , the text will also be > greyed. Lastly, if a new ticket matching the query criteria has been > created, it will be shown in bold.
What I did was to go the main wiki page and then click my display link which is a custom ticket query URL. So I was newly going to the page and the old stuff was still generated. I did not click "update"; perhaps that would get rid of the no-longer-matching tickets. It seems that this mode persists in the db, rather than on the page, which is not what I epxected. Thanks for the explanation. Greg -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
pgpA0ZJxPJ5jg.pgp
Description: PGP signature
