| 13 | | Relations between tickets are stored in a table called `Subtickets` with just two columns: ''parent'', ''child'' and that eases reporting considerably when compared to ChildTicketsPlugin (which currently has more configuration options). For further information on reporting, see SubticketsPlugin/Reporting. |
| | 13 | Relations between tickets are stored in a table called `Subtickets` with just two columns: ''parent'', ''child'' and that eases reporting considerably when compared to ChildTicketsPlugin. For further information on reporting, see SubticketsPlugin/Reporting. |
| | 14 | |
| | 15 | Since tickets can have multiple parents, the expressive power of SubticketsPlugin corresponds to that of MasterTicketsPlugin (ie. both allow tickets to be organised in an acyclic directed graph). The UI of MasterTicketsPlugin is mostly oriented towards linking up already-existing tickets while SubticketsPlugin's UI is mostly oriented towards top-down creation and inspection of a ticket hierarchy. |
