Defect #21021
closedCopying a Redmine issue does not allow change of Status
0%
Description
Although the form presented allows selection between existing status and default status, if the existing status is "Closed", the change is not accepted. As a result, the new Issue is created with the Status = Closed and the changes to Subject and Description not done.
Related issues
Updated by Olivier Houdas about 9 years ago
You should check your workflow (Administration\Workflow) for your role in the project in which you are testing.
I tested with an issue in a project on my test site, and it works perfectly fine, the copied task is changed from Closed to New.
Updated by Toshi MARUYAMA about 9 years ago
- Status changed from New to Needs feedback
- Priority changed from High to Normal
Updated by Roger Noble about 9 years ago
Have tried again with the same result.
I've modified the workflow to allow all users to change status from Closed to New. I can modify an existing Closed issue to New. But the copy does not allow the change. It accepts selection from dropdown but does not do the change.
The Redmine version is: 3.0.1.stable.
Updated by Toshi MARUYAMA about 9 years ago
I cannot reproduce, too.
I cannot see problem this code.
source:tags/3.0.6/app/models/issue.rb#L805
Please give us plugins you used.
See Submissions.
Updated by Go MAEDA over 7 years ago
- Related to Feature #23610: Reset status when copying issues added
Updated by Go MAEDA over 7 years ago
- Status changed from Needs feedback to Closed
- Resolution set to Fixed
Fixed by #23610 for upcoming Redmine 3.4.0.
Issue status is reset to default when an issue is copied and you can choose from all allowed statuses for a new issue.