closed_on missing when closed status of issue status changed
|Assignee:||Jean-Philippe Lang||% Done:|
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.
Fixed that setting a status as closed should update issue closed_on attribute (#18280).
add missing fixtures to test/unit/issue_status_test.rb