-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
47
-
Severity 1 - Critical
-
50
-
Issue Summary
When cloning an issue, if the Resolution field is already set, its value is copied into the new issue that was just created. This happens both for Classic and Next-Gen project.
Steps to Reproduce
- When accessing any issue, clicks on "..." and then on Clone
- The status of the just created issue will be set as the very first of the workflow, but its Resolution will be copied from the clone issue
Expected Results
The Resolution value should be cleared
Actual Results
The Resolution value is copied from the clone issue. This problem happens both in Next-Gen project AND Classic projects.
https://share.getcloudapp.com/Qwu0nPD9
Workaround
Both Next-Gen and Classic projects
Access the board and transition the issue to another status that is not Done/Resolved/Closed. Then, move the issue back to the very first status of the applied workflow:
https://share.getcloudapp.com/6quezd5z
For Classic projects
It's possible to add a post-function in the Create transition (right before the Create the Issues Originally post-function) in order to clear the Resolution field, as shown below:
- is related to
-
JRACLOUD-71893 Jira issues get a resolved time even at issue creation when a default resolution is set
- Closed
- causes
-
JST-599102 Loading...