Product Documentation

ExtraView maintains an accurate record of the date that each issue is closed. This is achieved by inserting the current system timestamp into the issue, when the issue is moved to the closed state. The closed state is defined by the behavior setting named STATUS_CLOSED_NAME. Its default value is CLOSED, but the administrator may change this. The value should only be changed during the implementation of a new system, as once data accumulates in a system, you will lose the historic references to when issues were closed, if you change this setting.

However, your workflow may (or may not) allow closed issues to be re-opened. The rules for setting the DATE_CLOSED date in the database are as follows:

1. The initial value for DATE_CLOSED is NULL. As long as the status of
   the issue is not set to the value of the STATUS_CLOSED_NAME behavior setting, DATE_CLOSED remains equal to NULL
2. If the Status is changed to STATUS_CLOSED_NAME, then DATE_CLOSED is assigned the value of the current date
3. If a user has write permissions the security permission key named PR_RESOLUTION.ALLOW_EDIT_CLOSED, and they change the status to a value other than STATUS_CLOSED_NAME, then DATE_CLOSED is reset back to NULL, until the issue is again changed to the status of STATUS_CLOSED_NAME.

Note: The field named DATE_LAST_STATUS_CHANGE always is initially set to the date that the issue is first created, and subsequently is only modified if the status changes value.