-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Approvals
-
None
-
2
-
Severity 3 - Minor
-
1
Issue Summary
This is reproducible on Data Center: (yes)
If we set approval back to back (from status to another status an approval is required), the previous approver will be added even though it is already removed from the approver field.
Steps to Reproduce
- Set the same Approval as in your Workflow setup with 2 Approval Status back to back.
- Create a ticket that will use the workflow.
- Set only 1 Approver when creating the issue and proceed.
- Login as the approver and approve/reject to move it to the next approval status.
- After moved, edit the Approver to another user.
- Expected Results
Expected Results
- The previous approval history will show the previous user while the current approval will be updated with the current user
Actual Results
- The current user somehow added to the Approver History of the previous approval status.
Workaround
. Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JSDCLOUD-11151 Changing approvers on an issue with multiple approval steps appears to change approval history for earlier approvals
-
- Closed
-