How to check if user is administrator using smart values?

[Eiríkur Baldur Þorsteinsson]

Hi,

I want to create an automation rule which goes through all request participants and checks if they are administrators.

The smart value {{RequestParticipant.emailAddress}} successfully delivers a participants email address, but how can I check if the participant's role is administrator?

Kind regards, Eirikur

[Kalyan Sattaluri]

Hello @Eiríkur Baldur Þorsteinsson 

RequestParticipant list, is that a user picker field?

In the If condition section, instead of comparing 2 values option, there is a user condition section which lets you check reporters/assignee/user are in admin role. Have you checked that option?

[Eiríkur Baldur Þorsteinsson]

Hi Kalyan,

RequestParticipant is a list of users in the issue field Request participants, which is a user picker field.

I cannot use the User condition because its User input does not take smart values.

[Kalyan Sattaluri]

To confirm, you dont see "Request Participants" as an option in the drop down? (highlighted below)

[Eiríkur Baldur Þorsteinsson]

That is correct. I don't see "Request Participants" as an option in the drop down.

[Kalyan Sattaluri]

Hmm. I cant think of a simple way and hoping others can pitch in and help.

But If what you want to know if is the user is of Admin role in a project, below thread tells you how to do that through REST calls. So if comfortable with making "send web request" action inside your branch, def review below thread in the mean time.

https://community.atlassian.com/t5/Jira-Software-questions/How-to-get-users-assigned-to-Jira-Project-and-their/qaq-p/2219936#M238087

[Eiríkur Baldur Þorsteinsson]

Thank you, Kalyan.

I have been able to make it work with send web request, but it seems like a lot of effort. I was hoping there was a simpler way, which did not require a user's email address and password or token, because it means that the automation stops working if the user gets disabled.

[Kalyan Sattaluri]

Great,  and agreed with the effort needed and especially the tight coupling to rule author's credentials.

Maybe its because of GDPR regulations that Jira does not have a easy way maybe?