right. We took the interesting (and I think in retrospect correct)
decision at the start of our trac usage to disable report module... has
meant I'm not relying on any those features, and have found it
(strangely) helpful (no intricate solutions),
We've just started used TracTags for that kind of stuff (component
hierarchies etc.). (though generally have used combinations of separate
short tags rather than relying on analysing longer tags. the new
expression language is very useful.
this is enabling us to mark a ticket with multiple sub-components
(because you can have many keywords on a ticket), though keepign large
component groupings still singular...
anyway... all that's not much use for you - sorry!
Tim
Russell Hind wrote:
I too use the query interface more now, the only issue is that we have
reports that do pattern matching on components e.g.
Component1/*
But there is no way to enter this in the query interface. I think the
query interface needs 'beefing' up a bit before it will be really useful.
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
