Low Summary
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 Result
- The previous approval history will show the previous user while the current approval will be updated with the current user
Actual Result
- The current user somehow added to the Approver History of the previous approval status.
Workaround
not yet found
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-6586] Previous Approver is added to the Approver History when a back to back approval is set
"We use Jira's approval system for compliance and security approvals. This is a pretty big issue for us, since our operations teams have issues telling when/where things are/were approved. " - This use case is true to us as well. Can we get some support on this?
Any movement on this? Looks like it's been pretty stagnant. This is starting to cause more nouse in our company, due to names showing up under different approval status when they shouldn't.
We use Jira's approval system for compliance and security approvals. This is a pretty big issue for us, since our operations teams have issues telling when/where things are/were approved.
Would love to see this fixed.
Hi cyilmaz, I've made my previous comment above available to public, please let us know if this does not resolve your issue
Thanks,
Lenard
Hi,
We are using Jira Service Management 4.9.1 and we also have this error. We have been waiting for this problem to be solved for a very long time.
Can someone make a statement on the subject?
Regards,
Hi jrahmadiputra,
It seems to be related to https://confluence.atlassian.com/adminjiraserver/configuring-jira-service-desk-approvals-938847527.html under `How it works` in the first point:
You can use the same field for more than one approval step, but we do recommend that if you need more than one approval step on the same workflow, you use different user picker custom fields for each approval step to avoid confusion.
It could be used as a possible workaround so that the custom field history does not get confused.
This bug is indeed not ideal if you need an accurate approval history recording. We would appreciate, if this could be fixed.
Thanks!