Modify ↓
Opened 13 years ago
Closed 13 years ago
#9184 closed enhancement (fixed)
Multiple parents for tickets
Reported by: | anonymous | Owned by: | Mark Ryan |
---|---|---|---|
Priority: | normal | Component: | ChildTicketsPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Attachments (0)
Note: See
TracTickets for help on using
tickets.
Hi
If you are looking to maintain a more complex hierarchy of tickets, you'd probably be better looking at MasterTicketsPlugin. For 'non-simple' parent/child relationships, I think MasterTicketsPlugin does a really good job and has the graphical tree to give a really good overview of the hierarchy.
I've avoided anything other than a simple parent(single)-to-child(multiple) relationship in this plugin in order to keep its function clearer (and simpler!), there are certain checks performed against the parent (ticket status, type, etc...) that would be difficult if performed against multiple parents.
Maybe you should re-think the structure of your tickets? In the example you gave above (I realize it's just an example!), I would express it as a single tree, like so:
ie. In order to move house, you need to first buy the new house and in order to achieve this, you need to send the money to the vendor.
At the end of the day, it's easy to get carried away with the ticket hierarchy and structure (ie. you can go into minute detail and have a very deep hierarchy!) and a balance needs to be found.
For the moment, I would rather keep this plugin as intended (parent-child).
Thanks for the feedback/input.
Cheers
Mark