Opened 19 years ago
Closed 18 years ago
#2743 closed enhancement (fixed)
Closing a milestone manually should retarget open tickets to other milestone of choice
| Reported by: | Owned by: | Matthew Good | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.10 |
| Component: | roadmap | Version: | 0.9.3 |
| Severity: | normal | Keywords: | |
| Cc: | macke@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
This should be very similar to deleting a milestone.
I could not figure out how to do this (the Trac-Trac seems to do this regularly) and I would find really it useful since a lot of issues haven't been fixed when we decide to close/release a milestone.
Attachments (1)
Change History (7)
comment:1 by , 19 years ago
| Milestone: | → 0.10 |
|---|
comment:3 by , 18 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
I tested with r3622 and it is working pretty good.
But when you rename the milestone and "Retarget associated open tickets to milestone" to another milestone at the same time, the open tickets still remain in the just closed milestone.
I think Trac just took the wrong milestone name to update the table. So just a hopefully small problem…
comment:4 by , 18 years ago
I just looked at the code and changed the position of the one line, where the milestone.name is assigned. Now it works really fine.
comment:5 by , 18 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
Ok, let's get this patch in.
comment:6 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Ok, patch committed in r3732. Thanks.
Yeah, that would be nice. (I thought we already had a ticket for this, but apparently not)