Defect #18280

closed_on missing when closed status of issue status changed

Added by Felix Schäfer almost 4 years ago. Updated almost 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Issues
Target version:2.6.1
Resolution:Fixed Affected version:2.6.0

Description

When the status of an existing issue status is changed to "closed", the closed_on column of issues that have or had that status is not set/updated. This causes a discrepancy between Issue#closed? that can be true with Issue#closed_on being null.

Tested and confirmed on trunk.

Associated revisions

Revision 13560
Added by Jean-Philippe Lang almost 4 years ago

Fixed that setting a status as closed should update issue closed_on attribute (#18280).

Revision 13569
Added by Toshi MARUYAMA almost 4 years ago

add missing fixtures to test/unit/issue_status_test.rb

Revision 13640
Added by Toshi MARUYAMA almost 4 years ago

2.6-stable: fix syntax error on Ruby 1.8.7 (#18280)

Revision 13641
Added by Toshi MARUYAMA almost 4 years ago

Merged r13640 from 2.6-stable to trunk (#18280)

History

#1 Updated by Jean-Philippe Lang almost 4 years ago

  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang
  • Target version set to 2.6.1
  • Resolution set to Fixed

Fixed in r13560.

#3 Updated by Jean-Philippe Lang almost 4 years ago

  • Status changed from Resolved to Closed

Merged.

Also available in: Atom PDF