Forums

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

Automation not triggering for "Bug" Issue Type

Rahul Khanna November 10, 2021

Hello,

 

Here's my use case:

Whenever a "Bug" is created in my team, I would like for a slack message to be sent to a specific channel.

 

What I did:

Screenshot 2021-11-10 at 16.13.08.png

 

This does not seem to work.

 

Interestingly, when I try the same automation with issue type as "Task", everything works fine.

 

I dug a bit more and found that if I create a "Bug" issue type, there was no entry in the audit log for the issue.

 

Any suggestions? TIA

3 answers

2 accepted

0 votes
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 10, 2021

Hi @Rahul Khanna 

If you are seeing the rule triggering in the log and the conditions not matching, this could be a timing issue where the data is not available at the time the rule fires.  This can happen with the issue created trigger.

To confirm/resolve this, please add a Re-fetch action immediately after the trigger and before the conditions.

Kind regards,
Bill

Rahul Khanna November 10, 2021

Hey Bill,

 

Thanks for your reply. 

The weird thing is: I am seeing logs and condition matching is correct as well. However, for Bug-type issue, there is NO entry in audit logs.

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 11, 2021

Just to confirm: when you create an issue of type "Bug" in the same project where the automation rule is defined and enabled, you do not see an entry in the audit log showing the rule triggered.  Correct?

Again I wonder if context and timing are related.  How are you creating the issue:

  1. from the top navigation bar Create button
  2. from the backlog's "Create issue" link
  3. from an epic's "+" button
  4. from an epic's "Create issue in epic" button
  5. from another automation rule
  6. from the REST API
  7. from a marketplace addon app UI

 

Also, is this a company-managed or team-managed project?

Rahul Khanna November 11, 2021

@Bill Sheboy 

That is correct.

I am creating the issue from the top navigation bar Create button

Not sure how to verify whether this is a company or team managed project. Can you please tell me how to check that?

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 12, 2021

If you expand the options on the left side of the page, you will see an indicator for the project type at the bottom of the page.

Would you also please check with your site admin if you have more than one issue type named "Bug"?  If so that could be causing the mis-match.

0 votes
Answer accepted
Callum Carlile _Automation Consultants_
Community Champion
November 10, 2021

Hi @Rahul Khanna , welcome to the Community!

Have you created this automation rule through the project setings or through the global section (System > Automation rules) ?

There should always be something in the Audit log whenever an issue (of any issue type) is created in the project(s) which your rule is scoped to. If there is nothing at all in the audit log when you create a bug, then it may be that the bug is being created in a project not associated with this automation rule. You can check this under Rule Details > Scope.

If there is an entry in the audit log but with an outcome of No Actions Performed, then it may be that the Squad doesn't equal "Buyers"?

If this automation rule is triggered by another autoamtion rule, then you will need to have this option ticked in Rule Details, otherwise the rule will not trigger.

checkbox.png

You can also troubleshoot by going to the issue itself and clicking on the Automation section, which will display all of the automation rules which the issue has triggered. Your rule should be displayed here for all issues, as they all should have triggered the rule. If not, then it might be the same issue as described above relating to the scope of the automation rule

automation.png

Rahul Khanna November 10, 2021

Hello @Callum Carlile _Automation Consultants_ 

Thanks for qiuck response:

 

On your points, the rule is created in project settings. Please check below screenshot:

Screenshot 2021-11-10 at 17.15.40.png

 

I then created another "Bug". You can see the project and squad in the screenshot below. Please notice the jira id.

Screenshot 2021-11-10 at 17.21.00.png

I tried troubleshooting and found that no automation rule has been applied.

Screenshot 2021-11-10 at 17.20.46.png

 

The audit log clearly show that the above created issue simply skipped the log queue. Check screenshot below:

Screenshot 2021-11-10 at 17.25.23.png

Rahul Khanna November 11, 2021
0 votes
Sebastian Krzewiński
Community Champion
November 10, 2021

Hi @Rahul Khanna 

 

Please check event on workflow for Bug issue type. It looks like workflow for bug trigger different event than created.

 

Seba

Rahul Khanna November 10, 2021

@Sebastian Krzewiński 

I checked and could see "Create" event on the workflow for Bug issue type. I also checked the same for Task issue type and it is the same.

Sebastian Krzewiński
Community Champion
November 13, 2021

@Rahul Khanna 

Can you share screenshot with all post functions and validators on create transition?

Suggest an answer

Log in or Sign up to answer