-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.3, 7.12.1
-
6.03
-
27
-
Severity 1 - Critical
-
6
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Steps to replicate:
- Create a project with a workflow that does not set the resolution at any point
- Change the edit screen so that it has the 'resolution' field on it
- Create an issue
- Edit the issue to set a resolution
Result:
Issue does not have a resolved date
Expected result:
The issue has a resolved date and resolutiondate in the database has been updated.
Workaround
The resolution field should be altered either through a post-function, or by a screen specifically used to resolve issues. You should not have the resolved field on the edit issue screen.
- causes
-
JIRAAUTOSERVER-960 Setting resolution field as an edit issue action does not set the resolved date of issue
-
- Gathering Impact
-
- relates to
-
JRACLOUD-39175 Changing a resolution by editing an issue does not set a resolved date
-
- Closed
-
- is related to
-
ACJIRA-1064 Loading...