-
Bug
-
Resolution: Fixed
-
Low
-
9.4.30, 9.12.0, 10.3.0
-
9.04
-
Severity 3 - Minor
-
Issue Summary
When performing a Jira transition with post function, if the post function sets a field value to the same value as the transition UI, then no change history is recorded.
Steps to Reproduce
- Create a new project using the process management template.
- Create a new issue within the project.
- Transition the issue through the workflow to the "Done" status.
- Set the resolution for the issue and verify that the resolution appears in the issue history.
- Edit the workflow and add a post function to the "Done" step to set the resolution.
- Transition the issue through the workflow to the "Done" status again.
- Set the resolution and check the issue history.
Expected Results
The issue history should correctly display the resolution change when the resolution is set during the workflow transition, regardless of whether it was set via a post function or manually
Actual Results
No issue history is shown for the field, only the Status
Workaround
- Move the post function step to after the issue history event, then the problem can be avoided as JSM will see the original history item.
- Remove the post function setting the field
- Remove the field set from the transition screen
- is related to
-
JSDSERVER-16082 Add a healthcheck or similar to warn Administrators if the post function configuration is not compatible with SLA configuration
- Gathering Interest
- resolves
-
JSDSERVER-16048 SLA does not stop if the "Resolution" has been set twice within a workflow transition
-
- Closed
-