automation issue for status chanes

[Anush Chatikyan]

Please help me find what's wrong with my automation , 

[Olga Videc]

Hello @Anush Chatikyan 

Let's start with this then will troubleshoot further.

First, your rule is restricted to ITDEV project, you need to edit the rule settings to multiple or global projects. The related issue is FO-836 is a different project.

When choosing the transition make sure you choose the right one if you have multiple workflows with transitions with the same name check the number next to the name of the transition so you choose the right one. 

Where is your resolution set in automation or on workflow?

BR, Olga

[Anush Chatikyan]

look, the issue is that when ithis field i m puting the matchig JQL only status= in progress it's working like no matter it's local rule or global , like when i am adding the seocnd status = bocked it's giving me error i guess the issue is with JQL  (as i want that if the linked tickets statuses will change in progress or blocked the main ticket went to under implementation ) @Olga Videc @Joseph Chung Yin 

[Joseph Chung Yin]

@Anush Chatikyan -

To supplement what @Olga Videc mentioned -

When you make an automation rule (global or associated with multiple projects), then you need to watch for the execution usage limits allocated to the different tiers based on your cloud subscription plan.  See following link - https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

In addition, you have to ensure all the issues WFs all have the appropriate WF status and transition to your specified status setup/established + the rule actor of your automation rule has the access and permission setup to conduct the transitions.  Otherwise it will not work properly.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.