Patch #23764
closed_on field of copied issue is always set to source issue's value
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | 3.1.7 |
Description
When we copy a closed issue, the value of "closed_on" of copied issue is always set to source issue's value, even if the status of copied issue is not closed. I think it should be nil because the copied issue have not been closed before.
Steps to reproduce:
1. Create a closed issue (Issue_A).
2. Click "Copy" on Issue_A.
3. Change status to "New" and create a new copied issue (Issue_B).
4. "closed_on" field of Issue_B should be nil, but the value is same with Issue_A.
clear_closed_on.diff 
- patch
(1.99 KB)
Related issues
Associated revisions
closed_on field of copied issue is always set to source issue's value (#23764).
Patch by Go MAEDA.
History
#1
Updated by Kohei Nakamura about 6 years ago
Thank you, Maeda san.
I think probably many people want to solve this problem.
I hope this patch will include in the next version Redmine.
#2
Updated by Yuuki NARA about 6 years ago
+1
#3
Updated by Jean-Philippe Lang about 6 years ago
- Target version set to 3.1.7
#4
Updated by Jean-Philippe Lang about 6 years ago
- Status changed from New to Resolved
- Assignee set to Jean-Philippe Lang
Committed, thanks.
#5
Updated by Jean-Philippe Lang about 6 years ago
- Status changed from Resolved to Closed
#6
Updated by Mischa The Evil over 5 years ago
- Duplicated by Defect #25151: Copied issues cause wrong reports: Original issue is added to report list although search criteria only match the copied issue and not the original issue added