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

Triggering user not appearing in automation

Dd_ccz4b8

I have a manual automation.

Even though I set the actor to be USER WHO TRIGERRED EVENT I always get Automation for Jira

I see the comment:

Due to security restrictions, there are certain users who cannot run 'User who triggered the event' rules as the rule actor. This includes users created by Marketplace apps and special admins. In these situations, the actor will be 'Automation for Jira' instead.

But there's nothing special about the users (not that I can tell).

What am I doing wrong?

Thanks

Accepted answers

Bill Sheboy

Hi @Dd

First thing: that is a generic warning message shown in the rule editor when the rule actor is changed away from the built-in, Automation for Jira user.

It displays because the built-in user has enhanced permissions beyond what is apparently possible to set for any customer-added user. And so rules could malfunction when another actor is used. Still, changing the actor is needed for edge cases, such as working around the licensing decisions for tools like Jira Product Discovery (JPD).

You note the following:

Even though I set the actor to be USER WHO TRIGERRED EVENT I always get Automation for Jira

Where are you seeing this and how is it impacting the behavior of your rule?

FYI, when you specifically want the user who triggered a rule, such as a manual one, please use the {{initiator}} smart value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/#--initiator--

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Dd

First thing: that is a generic warning message shown in the rule editor when the rule actor is changed away from the built-in, Automation for Jira user.

You note the following:

Even though I set the actor to be USER WHO TRIGERRED EVENT I always get Automation for Jira

Where are you seeing this and how is it impacting the behavior of your rule?

Kind regards,
Bill

Dd_ccz4b8

It's not impacting work per se, but when I want to check who triggered the operation that changed the value in a ticket, I get the automation (there was a time where it was the actual persona)

As for using the initiator smart value - what you mean is to add a comment (or maybe update a dedicated field) with that value?

That would work as well - might even be better as I ask the initiator to specify the reason behind the trigger.

Bill Sheboy

Thanks for that information.

What I was describing using the {{initiator}} smart value could be used as a comment, or could be used in rule conditions to control the actions, etc.

If you encounter more challenges with the rule, please post an image of the complete rule, the audit log details, and explain what is not working as expected.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

trigger

automatio