Project

General

Profile

Actions

Defect #31420

closed

issues-table; closed_on - column should be updated to NULL whenever issue's status is changed to a 'is_closed == 0' status

Added by Florian S. almost 5 years ago. Updated almost 5 years ago.

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

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

The column "closed_on" was filled in issues table for some issues that were not closed.

It seems as if the column gets filled with the current timestamp if the issue's status is changed to a status that is marked as "is_closes" 1 in status table.

Thats OK.

But if issues get changed back to a status that is not closed ("is_closed" 0) the issue column "closed_on" still is filled with the timestamp the status changed to a "is_closed" 1 status

Requested behaviour: If a issue gets a status that is "is_closed" 0 an issue has "closed_on" != NULL the "closed_on" column should be set to NULL.


Related issues

Related to Redmine - Feature #824: Add "closed_on" issue field (storing time of last closing) & add it as a column and filter on the issue list.ClosedJean-Philippe Lang2008-03-10

Actions
Actions

Also available in: Atom PDF