Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation works for me but not for other users

Anastasia Seidaridi
Contributor
November 16, 2022

Hello community,

I have set some automation rules that are shared by multiple projects. When I test them, they work just perfect for me, but when someone else tries the same thing it is not working. Any ideas how to solve this?

Thank you 

3 answers

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.
November 16, 2022

Hi @Anastasia Seidaridi 

Would you please clarify what you mean by they work for you and not for others?  What do you observe?

What type of projects are these rules running for: company-managed, team-managed, or both?

For a question like this, I suggest posting images of your complete automation rule, including the information from the rule's details section at the top, and images of the audit log details showing what happens when the rule executes as successfully, or not.  That information will provide context for the community to help.

Kind regards,
Bill

Anastasia Seidaridi
Contributor
November 17, 2022

Hello @Bill Sheboy

Here is one of the rules. It is to copy some specific fields from Epic to Story.

Screenshot 2022-11-17 at 8.43.06 AM.png

Here is also the audit log where I can see success and no actions performed.

Screenshot 2022-11-17 at 8.39.19 AM.png

 

And below is the example of the field that should be copied. When I perform the above action (create a story in the epic) then the filed is copied as it should. When someone else does the same exact thing, the field stays blank. All the projects that share this automation are company-managed.

Screenshot 2022-11-17 at 8.44.12 AM.png

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.
November 17, 2022

Thanks for that information.

Let's first try the simplest thing which could fix this symptom:

  • The issue created trigger can fire fast...so fast that the data is not available when the condition tests the issue type...and so the condition fails.
  • The work-around for that is to add a Re-fetch Issue action immediately after your trigger.  That will slow down the rule a bit, and reload the data before attempting the condition test.

 

If that does not help...

Would you expand the details (Show more) in the audit log for an example that showed success and another which showed "no actions", and post that image?

It would appear the condition is not being met, and the log will confirm that.

And, would you please confirm the types of the projects for the issues: company-managed, team-managed, or one of each?

Anastasia Seidaridi
Contributor
November 18, 2022

Thanks @Bill Sheboy

It seems to work now, it just seems that it works faster for me than for others for some reason. Thank you very much for your help :)

Like Bill Sheboy likes this
0 votes
Trudy Claspill
Community Champion
November 17, 2022

Hello @Anastasia Seidaridi 

Who is specified as the Actor for the rule?

What do you mean by "not working" for other users?

Is the rule triggered for other users?

If it is triggered for other users, are you not getting the expected results?

If it is triggered for other users, please go to the Audit Log and click the Show More to the right of an entry that is for execution of the rule by a user where you did not get the results expected. Then show us what that audit log entry says. 

0 votes
Anastasia Seidaridi
Contributor
November 16, 2022

.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events