Brian McCann wrote: > Hi, > > Is there a way to manage components in Trac? > what if you want to have a Main Component with sub-components like > > First component > sub1 > sub2 > sub3 > > Second Component > sub1 > sub2 >
Not yet, but see #548 and http://trac.edgewall.org/query?status=new&status=assigned&status=reopened&keywords=%7Ehierarchy > > Is there away to do this? Priorities and Ticket type have a way to order items > even if you number them 1.0 1.1 ...9.0 9.1 once you get to 10 Trac can't > handle it and puts > 10.0 up with the 1.0 component Those are Trac "enums", and as such are ordered by their "values", not by their names. This is meaningful for priorities, but for ticket types, it's more an implementation artifact, as the values are never used. Components are handled separately and they may even become Trac resources on their own in the future, so I'd suggest taking the "hierarchical structuring" route, which is the most likely to become supported. Besides, we'll probably also support "natural sort order" for those names, in order to cope with the "1.0 10.0 9.0" issue you mentioned. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
