Forums

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

Automation rule not getting triggered when field value changes

danish.khatri October 24, 2024

Hello,

Can someone help me understand if the rule i have created is incorrect or its automation nodes getting failed and because of which the rule is not getting triggered.

Below is my rule and i want to update priority for issue type "Bug" between Jira Software Project & Jira Service Management Project and they are both linked by following types : cloned by and clones.

 2024-10-24 10_20_46-Clipboard.png

But when i update the value of priority in Jira Software Project it is not updating the value in Jira Service Management Project for the issue type Bug and also there is no log generating which can tell me if my rule was failed or incorrect.

Additionally i have created similar rule for Issue type "Task" and its working fine.

From the Atlassian community i found the following article 

https://support.atlassian.com/automation/kb/automation-for-jira-troubleshooting-guide-for-situations-where-automation/

is there anything else i can do to make my rule work? Please let me know.

Thanks

1 answer

0 votes
Yash_reddy
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.
October 24, 2024

Hi @danish.khatri 

Welcome to Atlassian Community

What is the project scope you have defined in the rule details of automation?

Yash_reddy
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.
October 24, 2024

Do you have "Bug" issue type in the JSM project?

danish.khatri October 24, 2024

both Jira Software Project and Jira Service Management 

danish.khatri October 24, 2024

Yes JSM has issue type as Bug

danish.khatri October 24, 2024

Here is the rule i created for Issue type "Task" with same logics and conditions and its working fine.

2024-10-24 10_34_00-Clipboard.png

Yash_reddy
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.
October 24, 2024

can you share the Audit log where it triggered

danish.khatri October 24, 2024

That is the thing no Audit log were triggered for Bug 

Yash_reddy
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.
October 24, 2024

I understand it didn't perform change. Do you have Audit log in the rule. So it helps to check further. 

I would suggest to check these below:

1. If the issue where priority changed have Bug linked.

2.Bug have priority field in screen

danish.khatri October 24, 2024

Audit log never got generated for this rule. just shows me config changes that's all 

danish.khatri October 24, 2024

I initially created this rule and when it was not working so my Jira admin suggested since they couldn't check the automation nodes instead asked me to recreate the rule here is the audit logs for both the times i have created the rule for 

1st first time when i created the rule then turned off and created new rule 

2024-10-24 10_43_33-Clipboard.png

New rule audit log

2024-10-24 10_46_24-Clipboard.png

To answer your questions,

1. If the issue where priority changed have Bug linked. --> Yes they are linked via type cloned by and clones and there are other rules for issue type Bug like updating root cause which is also working fine.

2.Bug have priority field in screen --> Yes Bug has priority field in both Jira Software Project and Jira Service Management Project 

 

Yash_reddy
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.
October 24, 2024

@danish.khatri  Is the rule enabled?

danish.khatri October 24, 2024

Yes it is enabled and globally set for both the projects

2024-10-24 11_02_21-Clipboard.png

Ponnappan Ganapathiya
Contributor
October 24, 2024

1. Is there is any other restrictions you put on the trigger.

2. Other rules interfere with this. if any click on check to allow other rules to trigger this in the rule details page.

danish.khatri October 24, 2024

Like i mentioned there are 2 separate rule to sync priority for Issue type Bug and Task. do you think i need to enable the check box to allow other rules to trigger this as they are independent of how they are triggered?

Ponnappan Ganapathiya
Contributor
October 24, 2024

Assume, if the priority of Bug issue type is changed by other automation rule, not manually means you should have checked that box.

danish.khatri October 24, 2024

so the trigger point for priority of Bug is when someone edits the field and then it should update the priority in other project as well.

But i believe since task and bug are using same priority field and each of them has condition of checking issue type i think when executing rule for bug since task rule has been executed with condition as issue type only task hence its not executing for bug.

I will enable the checkbox to allow it to execute when other rules is executing.

Like Ponnappan Ganapathiya likes this
danish.khatri October 24, 2024

@Ponnappan Ganapathiya I enabled the checkbox but the rule still didnt worked no audit logs generated as well.

danish.khatri October 24, 2024

I am thinking of merging the Task & Bug Priority rule together and hoping it should work.

I just have to update the rule condition logic as below

2024-10-24 17_24_50-Clipboard.png

Suggest an answer

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

Atlassian Community Events