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.
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
is there anything else i can do to make my rule work? Please let me know.
Thanks
Welcome to Atlassian Community
What is the project scope you have defined in the rule details of automation?
Do you have "Bug" issue type in the JSM project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is the rule i created for Issue type "Task" with same logics and conditions and its working fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you share the Audit log where it triggered
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Audit log never got generated for this rule. just shows me config changes that's all
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
New rule audit log
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@danish.khatri Is the rule enabled?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Assume, if the priority of Bug issue type is changed by other automation rule, not manually means you should have checked that box.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ponnappan Ganapathiya I enabled the checkbox but the rule still didnt worked no audit logs generated as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.