Mr. Meitar Moscovitz wrote: > This creates a very loose concept of a "superticket" and a > "subticket", but does not cause the software to enforce any kinds of > dependencies or workflow on these tickets, which is what we want. > Nevertheless, this is extremely useful because then traditional > queries can reference "all subtickets" of a ticket simply by using a > query like one in the following example (which shows subtickets for > ticket:13): > > [[TicketQuery(kewords~=#13)]] > > To any supertickets in our projects, we typically add this TicketQuery > macro at the end of the ticket description so that the ticket > description itself contains a listing of all its subtickets.
This is a very interesting idea, thanks for sharing! The only drawback I see is that your query "keywords~=#13" will match all subtickets of #13, #130, #131, #132, ... which is probably not what you want. A new match operator for "contains the word ..." would be useful. -- Remy
signature.asc
Description: OpenPGP digital signature
