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

Get Rule Actor of a project automation rule in Scriptrunner custom script validator

KL Kumar

Hello!

I'm using automation rule (Automation for JIRA addon) in my project. Now I need to get the Rule Actor of my automation rule in scriptrunner custom script validator. This is because I do not want to run the validation when the rule actor is on my name.

I tried using the currentUser in my script. But this always returns the current login user and not the Rule Actor.

Is there a solution for this problem?

Accepted answers

All comments

Mark Chaimungkalanont

Hey there,

I think you should be able to use:

{{rule.actor}}

Hope that helps!

Cheers,

Mark C

KL Kumar

@Mark Chaimungkalanont , Thanks for the reply.

I am getting the attached error in my script validator using {{rule.actor}

Gareth Cantrell_7nagel

The correct binding variable to use with ScriptRunner is currentUser (see here for more).

For example:

def ruleActor = currentUser

KL Kumar

@Gareth Cantrell, currentUser returns JIRA logged-in user. But not the Rule Actor of my automation user.

From the scriptrunner documentation, I could see the below code. When I try to test this code in my scriptrunner custom script validator, I get the error because ruleContext is not defined.

log.warn ("Initiator of the action was... " + ruleContext.renderSmartValues('{{initiator}}'))

How can I import ruleContext?

Gareth Cantrell_7nagel

@KL Kumar you are trying to use a smart value rather than the script binding variable.

The smart value {{initiator}} is specific to the automation rule and returns the user who initiated the rule, and is not necessarily the rule actor!

ScriptRunner, on the other hand, binds the rule actor to the currentUser variable in the script:

log.warn ("Rule actor is... " + currentUser)

Additionally, if you're getting an error when trying to use ruleContext, you are most likely using an older version of either ScriptRunner or Automation for Jira.

If you're using the latest versions of both apps, the following code should work to show the difference (using a manually triggered rule where the rule actor and the initiating user are different):

log.warn ("Rule actor is... " + currentUser + ", Rule initiating user is... " + ruleContext.renderSmartValues('{{initiator}}') )

KL Kumar

@Gareth Cantrell , Thanks for the reply.

I upgraded both the plugins to latest.

Scriptrunner for Jira - 6.17.0
Automation for Jira - 7.2.4

Still I get the error as undefined. Am I still making mistake anywhere!

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira

jira-software

addon-com.codebarrel.addons.automation

jira-server

automation