[Trac] Hierarchical database for tickets: component, version, etc.

[Roy Yves]

Does TRAC support hierarchical database for tickets.

For example, I might want to have version 1.1 and 1.2 for component A, but 2.35.1, 2.35.2 and 2.36.0 for component B:

Also, I might want to have listed component A and B if the user selects, for example, a package X (value of an custom field), and component C, D and E listed if user selects package Y (another value of same custom field).

To illustrate, when entering a ticket, if a user select package X, the component field will offer (only):
A
B

if then user selects comonent B, the version field will offer (only):
1.1
1.2


Anybody have an answer?

Thanks
Yves