Workaround for the myPending(), pendingBy() bug?

[Mikael Sandberg]

Does anyone have a good workaround for JSDCLOUD-5596 (myPending, pendingBy bug? We have a procurement workflow that requires approvals from multiple people before the ticket can be transition and not being able to report on who still needs to approve a ticket is bit of a pain. Does anyone have a good workaround for it?

[Angélica Luz · Accepted solution]

Hello Mikael,

Thank you for your question.

I’m afraid to say that currently, there is no workaround for that. 

I tested on my local site and doesn’t matter if it’s filtered by a single user (using the account id), it will show all tickets pending approvals. I also checked the automation thinking of copying the value of the field or sending an email, but I didn’t find the option to remove who already approved.

For now, it’s possible to see who still needs to approve directly on the ticket or via API using: https://xxxxxx.atlassian.net/rest/servicedeskapi/request/IT-123/approval

Other than that, there are no other options we can think of for now.

Kind regards,
Angélica

[Mikael Sandberg]

Thanks @Angélica Luz I suspected that. I assume that when someone approves it triggers a edit event, correct? If so then I should be able to work around it by trigger a web request and use tray.io to get the pending approvers and return that to Jira via an incoming web hook that update a field on the ticket.

[Angélica Luz]

I tested here and it doesn’t update the issue. I added more than one approver and approved with only one account. Nothing was added to the ticket history and the Updated X minutes ago also didn’t change.

[Mikael Sandberg]

Okay, that is what my testing shows as well. I guess I could run a script on a schedule  to see if approvals are still pending. Thanks for checking @Angélica Luz!

[Mikael Sandberg]

Just to follow up on this if anyone else is looking for a solution for this. This is how I solved it. You can use Search for issues using JQL (GET), the JSON result contains approvals. I then filter out the ones that are still pending and use an incoming web hook automation to populate a multi user pick list on the request.