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; } } }

How to restrict a user can not approve own request in JSM

Benjamin Zhou

In my JSM, if affected user and approvers are the same person, it means this user can approve own request. Does anyone can share some idea with me? How to restrict a user can not approve own request?

The field type of Affected user is assets objects. the field type of approvers is user picker(multiple user)

Screenshot 2026-05-26 114341.png

Accepted answers

All comments

Arkadiusz Wroblewski

Hello @Benjamin Zhou

Automate Reporter Assets Field in JSM Cloud | Jira and Jira Service Management | Atlassian Support

Assign Approvers Automatically with Asset Attributes in Cloud | Jira and Jira Service Management | Atlassian Support

This KB Articles should be Informative for you.

You can use the native Exclude approvers from setting on your workflow's approval step, but it only accepts standard Jira User Picker fields, not Assets object attributes.

Create a hidden User Picker field and use Jira Automation to copy the user account out of your Assets object into it. Then, add that new helper field to your workflow's approval exclusion list. Just remember that you'll need global Jira Admin rights to edit workflow approvals, and be sure to set up a fallback routing rule in case the affected user happens to be the only listed approver on the ticket.

Best,

Arkadiusz

Benjamin Zhou

@Arkadiusz Wroblewski thank you so much for the link shared. I am sorry I can not change the field type, and also, I can not make the change on "affected user" and "approvers". If so, to restrict a user can not approve own request in JSM, what I should do?

Shreyas_Quietmill

Hi @Benjamin Zhou You don't need to change either field - you need one extra hidden field that mirrors the Assets object's user, because the native "Exclude approvers" setting only speaks user-picker.

The pattern:

1. Create a new user picker field (call it "Affected person (user)") and keep it off the portal form entirely - requesters never see it.
2. Automation rule: when issue created (or when the Affected user Assets field changes), set "Affected person (user)" from the user attribute of the Assets object. The Atlassian KB "Automate Reporter Assets Field in JSM Cloud" that Arkadiusz linked shows the smart-value syntax for pulling an attribute out of the Assets object.
3. In your workflow's approval step, set Exclude approvers = "Affected person (user)".

Now the person the request is about physically cannot appear as an approver, enforced by the approval step itself rather than by hoping nobody notices. Your existing fields stay untouched - the mirror field is additive, which usually gets past the "we can't change the form" constraint, because you aren't changing anything anyone sees.

Benjamin Zhou

@Shreyas_Quietmill thank you very much for your reply. I read through your answer, after that I have a concern, please feel free to let me know if my understanding is wrong. I am using cloud, JSM, not JIRA. I want users to get a error notice before they submit a request when Affected user (asset object)= approver. If I use your method, it looks like it will take effect after user submit the request, because automation will run after the request is submitted. Am I right?

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-management-cloud

jira-service-management