Project

General

Profile

Actions

Patch #23764

closed

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

Added by Go MAEDA over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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.


Files

clear_closed_on.diff (1.99 KB) clear_closed_on.diff patch Go MAEDA, 2016-09-05 11:19

Related issues

Has duplicate Redmine - 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 issueClosed

Actions
Actions #1

Updated by Kohei Nakamura over 8 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.

Actions #2

Updated by Yuuki NARA over 8 years ago

+1

Actions #3

Updated by Jean-Philippe Lang over 8 years ago

  • Target version set to 3.1.7
Actions #4

Updated by Jean-Philippe Lang about 8 years ago

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

Committed, thanks.

Actions #5

Updated by Jean-Philippe Lang about 8 years ago

  • Status changed from Resolved to Closed
Actions #6

Updated by Mischa The Evil almost 8 years ago

  • Has duplicate 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
Actions

Also available in: Atom PDF