#9024 closed enhancement (wontfix)
Workflow issue when reopeining subtickets
| Reported by: | Owned by: | Mark Ryan | |
|---|---|---|---|
| Priority: | normal | Component: | ChildTicketsPlugin |
| Severity: | minor | Keywords: | workflow |
| Cc: | Trac Release: | 0.11 |
Description
Hi, i would deem it an enhancement as there are probably only a few people who stumbled upon the following behaviour (if any at all): When you try to close a ticket having subtickets that are not yet closed - trac telss you and rejects the close. However, it is possible to reopen a closed ticket, whose parent is also closed. That seems inconsistent - but i am not able to decide wether i would like it mor if trac refuses to perform the reopen or if trac should automatically reopen all parent tickets in this case. Perhaps one of the situations where a new configuration property would come in handy?
Attachments (0)
Change History (5)
comment:1 Changed 13 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 Changed 13 years ago by
PS. In the newer plugin the re-open of a child ticket is simply refused - I also thought about whether to re-open the parent too but simply refusing it, allows more flexibility in other situations where the parent is 'invalid'.
Hi
This is only a problem for trac 0.11. In trac 0.12, there are new extension points (TicketChangeListener) that make it pretty easy to reject a reopen based on a parent being closed. (It basically looks for an 'invalid' parent so should catch other 'problems' too...)
As you say above, I'm not sure how many people have this problem (although I did have it a few times in my old job!)
The internals of 0.12 plugin are quite different to 0.11 so it's not a simple job to get it working (in the same manner!) for 0.11.
I'll close this as a 'wont fix' (as the ticket is raised against 0.11), but this should NOT be a problem for the plugin supporting trac 0.12
Regards Mark (Walnut)