On Wed, May 29, 2013 at 6:12 PM, Gary Martin <[email protected]> wrote: > I'm actually hoping that there is a quick way to collect all the existing > patterns of relevance rather than worrying about justifying whether to > include them. This should also help if there are any future additions to > syntax for any reason.
It would be great, if we could automatically generate all possible TracLinks that resolve to a specific resource and then index all those representations, but I do not know, if this is possible. > It may be that this kind of query becomes more useful as the number of > tickets involved grows. Something useful to know might be all the tickets > that block another ticket but are not blocked. Perhaps I should check if > this kind of thing has already been implemented! If you use relation dependson/dependent to mark your blokers, the following query will return tickets that block other tickets, but are not blocked themselves: dependent:* AND NOT dependson:*
