-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
1
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
Whenever the Resolution field is updated, the Resolution Date is updated accordingly. This will mess up the statistics or reports especially for resolved cases.
There are some situations where the Resolution value is set but the request is not closed yet, and when the request is closed, the Resolution value is updated. The Resolution Date will be updated twice but the first Resolution Date is the real date for a request to be 'resolved'. However, it's not possible to retain the first Resolution Date.
Suggestion
A way to update the Resolution field without affecting the Resolution Date
- relates to
-
JRACLOUD-63100 As an admin, I would like to be able to change the Resolution value without updating the Resolution Date
- Closed
As an admin, I would like to be able to change the Resolution value without updating the Resolution Date
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
1
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
Whenever the Resolution field is updated, the Resolution Date is updated accordingly. This will mess up the statistics or reports especially for resolved cases.
There are some situations where the Resolution value is set but the request is not closed yet, and when the request is closed, the Resolution value is updated. The Resolution Date will be updated twice but the first Resolution Date is the real date for a request to be 'resolved'. However, it's not possible to retain the first Resolution Date.
Suggestion
A way to update the Resolution field without affecting the Resolution Date
- relates to
-
JRACLOUD-63100 As an admin, I would like to be able to change the Resolution value without updating the Resolution Date
- Closed