Patch #23764

closed_on field of copied issue is always set to source issue's value

Added by Go MAEDA 8 months ago. Updated 7 months ago.

Status:ClosedStart date:
Priority:NormalDue 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 Magnifier - patch (1.99 KB) Go MAEDA, 2016-09-05 11:19


Related issues

Duplicated by Redmine - Defect #25151: Copied issues cause wrong reports: Original issue is adde... Closed

Associated revisions

Revision 15848
Added by Jean-Philippe Lang 7 months ago

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 8 months 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 8 months ago

+1

#3 Updated by Jean-Philippe Lang 8 months ago

  • Target version set to 3.1.7

#4 Updated by Jean-Philippe Lang 7 months ago

  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang

Committed, thanks.

#5 Updated by Jean-Philippe Lang 7 months ago

  • Status changed from Resolved to Closed

#6 Updated by Mischa The Evil 2 months 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

Also available in: Atom PDF