Modify ↓
#6867 closed enhancement (duplicate)
Ticket may relate to more than one component
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.11b1 |
| Severity: | major | Keywords: | ticket component |
| Cc: | jason.guild@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
After using Trac for the past month, I've run into multiple occasions where I've wanted to add multiple components to a ticket. Some issues impact multiple components and you should be able to indicate that.
Attachments (0)
Change History (2)
comment:1 by , 18 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:2 by , 18 years ago
An alternative: We use the MasterTicketPlugin. We have one ticket for the complete thing. From that we create sub-tickets for each task. Thus, changing componentA gets one ticket and changing componentB gets another ticket.
Note:
See TracTickets
for help on using tickets.



Duplicate of #221