Steffen Hoffmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Chris Nelson wrote: >> Steffen Hoffmann wrote: >>> Chris Nelson wrote: >>>> [...] >>>> Any thoughts on how you'd want to do that? By milestone? By >>>> owner? By date range? If nothing is specified, all open tickets? >>> I'd do it same way as I did ticket selection in >>> WikiTicketCalenderMacro. You may wish to take a look at >>> corresponding revisions here: >>> >> http://trac-hacks.org/log/wikiticketcalendarmacro?rev=8272&stop_rev=8270 >>> Original idea is not mine, but I still think of TracQuery as a >>> sophisticated ticket selection, and you don't have to document and >>> learn new syntax as it is already known by many Trac users. >> >> A standard query mechanism is a good idea. But... >> >> 1. The only thing I see about TicketQuery() at the link you provide >> is a comment. > > Well, extending the selection to include all changes between [8270] > and [8272] and hitting <View changes> button should bring you there.
That helped. Thanks. (I assumed that your specific link would include the full range of relevant changes.) >> 2. How do you handle things Trac doesn't know about yet like >> children? I'd like some way to say, "Show ticket 1234 and all its >> descendants." > > This is a quite different subject. Yes. Since jsGantt shows parent/child but Trac doesn't support it natively, I want some configurable mechanism to have Trac-jsGantt know and follow parent/child relationships. And dependencies, now that I think of it. My immediate implementation will be based on Subtickets and MasterTickets but should be configurable or portable to the TracLinks(?) branch. I also have to deal with due dates in a flexible fashion. >... -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
