-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Approvals
-
None
-
1
-
Severity 3 - Minor
-
1
Issue Summary
When leveraging the Guard Premium Audit logging functionality, Approval actions in JSM related to Change Requests are logged. However if the Approval Customer Notification is configured with "Approvers can use 'Approve' and 'Decline' buttons without being signed in", the user that performed the approval/rejection is logged in the Audit log inconsistently. Sometimes the name shows up as the Actor, sometimes it doesn't, even though in the Work Item history there is always a record of the user that took the action. This inconsistency happens when the approval is done in the same manner (user not being logged in to JSM).
Steps to Reproduce
- Configure a Space that includes a Change Management Approval workflow (the template JSM space will work).
- Configure the Customer Notifications for the "Approval Required" to leverage the "Approvers can use 'Approve' and 'Decline' buttons without being signed in" option.
- Create a few work items and push them to the Approval Step
- Alternate Approving and Rejecting the items from the email buttons without the user doing the approval/rejection being logged in.
- Review the site wide Audit Log after those are completed
Expected Results
If the user name is logged on the work item history as having approved or rejected the approval, the same user should be added to the audit log as well as the actor of that event.
Actual Results
Sometimes the user is recorded as the Actor of the event that notes "Completed approval of change request...." other times it is just noted as "Jira Atlassian App" as the actor.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available