#2629 closed enhancement (duplicate)
Only retarget "open" tickets when deleting a milestone
| Reported by: | dju` | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.9.3 |
| Severity: | normal | Keywords: | |
| Cc: | dju@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I'd like to be able to only retarget open (ie not closed) tickets to the new milestone, because I think closed tickets for the current milestone have no reason to be retargeted to the new milestone (they are already resolved for the version being released!).
Attachments (0)
Change History (5)
comment:1 by , 19 years ago
| Cc: | added |
|---|
comment:2 by , 18 years ago
Replying to dju`:
I'd like to be able to only retarget open (ie not closed) tickets to the new milestone, because I think closed tickets for the current milestone have no reason to be retargeted to the new milestone (they are already resolved for the version being released!).
hope this will be solved soon
follow-up: 4 comment:3 by , 18 years ago
Replying to dju`:
I'd like to be able to only retarget open (ie not closed) tickets to the new milestone, because I think closed tickets for the current milestone have no reason to be retargeted to the new milestone (they are already resolved for the version being released!).
Usually if you are releasing a version/milestone, you are not simultaneously deleting it. You are instead just "closing" the milestone for future development.
It sounds like what you are really asking for is #525 - batch modification functionality.
follow-up: 5 comment:4 by , 18 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Replying to sid:
Replying to dju`:
I'd like to be able to only retarget open (ie not closed) tickets to the new milestone, because I think closed tickets for the current milestone have no reason to be retargeted to the new milestone (they are already resolved for the version being released!).
Usually if you are releasing a version/milestone, you are not simultaneously deleting it. You are instead just "closing" the milestone for future development.
That would be #3734.
So the functionality requested here would be better fulfilled with either #525 or #3734, as deleting a milestone should be a rare operation and should really mean removing it, not phasing it out.
comment:5 by , 18 years ago
Replying to cboos:
Replying to sid: …
Usually if you are releasing a version/milestone, you are not simultaneously deleting it. You are instead just "closing" the milestone for future development.
That would be #3734.
More precisely, #3734 is a request to add an intermediate "freeze" state, to prevent new tickets to be assigned to a still opened milestone, while we already prevent new tickets to be filed against closed milestone (#1078).
adding myself to cc