Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Is there a way to find A4J rules by a specific actor?

I have found by chance an Automation 4 Jira (Server) rule that does not have our technical user as actor, but a (former) employee (user deactivated).


Is there a way to find rules by a specific actor or - better - NOT having our technical user as actor?


Solutions including searches in the Jira DB are fine, too! :-)




1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 16, 2021

Hi @Thiemo Hiecke -- Welcome to the Atlassian Community!

I do not believe that is possible yet, based upon this suggestion:

One work-around would be to export all rules to JSON, and then search the results for what you need to know.  We did that to find use of certain custom fields and other things.

Best regards,


Darryl Lee
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2021

Re: JSON, I've had to do this very thing. So there's a very powerful tool called jq that parses JSON and lets you filter/format it however you like.

But for something like this, I just used its rudimentary "prettifying" feature, and then combined it with good old egrep:

jq . automation-rules-202008312215.json | egrep '^ "name":|username'

So, jq . takes the unformatted JSON export of all rules, and formats it all pretty, with one attribute per line, indented nicely.

Then egrep searches for lines that start with: [4 spaces]"name":

OR contain: username (you would replace this with the username you're searching for)

You should then end up with a list of EVERY rule, and if the username shows up anywhere in that rule, it will be listed after that rule, so like:

  "name": "Auto assign on transition"
  "name": "Balance support load for team",
    "value": "johndoe"
  "name": "Offboarding - Sub Tickets Creation",
    "value": "johndoe"
    "value": "johndoe"
Like # people like this

Hi @Bill Sheboy and @Darryl Lee

thanks for your replies! Exporting to JSON is really a good workaround with some more potential for administrating rules. And I will definitely take a look at jq.


Kind regards,


Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events