nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

A customer can approve his own application ! How can this be prevented ?

Michaël Monserrat

Hello,

We want to implement approval on a WF.

Currently, we let the client select the approver from the client list.

I noticed that the client could select himself and approve his own application!

Is it possible to prevent this?

Thank you, in advance, for your advice.

Best regards.

Accepted answers

Jack Brickey

yes I think this is an issue. if your client is both an approver and a requestor and you allow them to pick from the available approvers then their name is in the list too. You might be able to use Automation to test for self-approved and transition back to the approval status and issue comment saying "no no no...you can't self-approve".

All comments

Mohamed Benziane

Hello @Michaël Monserrat

If you are using a user picker (single choice) you can limit wich user will be available.

https://confluence.atlassian.com/adminjiraserver073/configuring-a-custom-field-861253383.html#ConfiguringaCustomField-userfilteringUserFiltering

You can filter by group or project role

Jack Brickey

Mohamed Benziane

Good idea to use Automation, i didn't think about it!

Michaël Monserrat

I had thought of this solution, but it seemed so obvious to me to prevent this type of action that I think Jira SD would handle it natively. I was hoping I'd missed a setting...

I confirm that it works correctly with Automation.

Thanks again for your suggestions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud