Discussion:
[Trac-dev] showing closed tickets when not asked for
Greg Troxel
2015-09-16 12:04:30 UTC
Permalink
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?
--
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 trac-dev+***@googlegroups.com.
To post to this group, send email to trac-***@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
Peter Suter
2015-09-16 16:27:54 UTC
Permalink
Post by Greg Troxel
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
Post by Greg Troxel
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.

If that's what you mean, the next sentence there mentions the intended
Post by Greg Troxel
The query results can be refreshed and cleared of these status
indicators by clicking the Update button again.

I personally found this rather confusing initially, but once it's known
I learned to ignore it.

[1] http://trac.edgewall.org/wiki/TracQuery#NavigatingTickets
--
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 trac-dev+***@googlegroups.com.
To post to this group, send email to trac-***@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
Greg Troxel
2015-09-16 21:49:01 UTC
Permalink
Post by Peter Suter
Post by Greg Troxel
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
Post by Greg Troxel
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 trac-dev+***@googlegroups.com.
To post to this group, send email to trac-***@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
RjOllos
2015-09-21 23:36:49 UTC
Permalink
Post by Peter Suter
Post by Greg Troxel
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
Post by Greg Troxel
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.
If that's what you mean, the next sentence there mentions the intended
Post by Greg Troxel
The query results can be refreshed and cleared of these status
indicators by clicking the Update button again.
I personally found this rather confusing initially, but once it's known
I learned to ignore it.
[1] http://trac.edgewall.org/wiki/TracQuery#NavigatingTickets
I found it confusing as well, though I appreciate it as a feature now that
I know about it.

I found one related ticket: http://trac.edgewall.org/ticket/9006
and I can confirm the defect noted by Remy in comment:5 - there is no
greying for tickets no longer match the query. The bolding of new tickets
works as described. We should probably reopen #9006 to address the greying
for tickets that no longer match the query.
--
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 trac-dev+***@googlegroups.com.
To post to this group, send email to trac-***@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
Loading...