Tim Diggins wrote:
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!
Well maybe it is. Only came across TracTags last week so am planning on
taking an in-depth look at them when I get a minute. We have nested
components because we have multiple products in our repo.
Your idea of having a single component for each product and then using
keywords for the area in that product seems like a good idea.
Cheers
Russell
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
