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:
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
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
Also, is this a company-managed or team-managed project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Callum Carlile _Automation Consultants_
Thanks for qiuck response:
On your points, the rule is created in project settings. Please check below screenshot:
I then created another "Bug". You can see the project and squad in the screenshot below. Please notice the jira id.
I tried troubleshooting and found that no automation rule has been applied.
The audit log clearly show that the above created issue simply skipped the log queue. Check screenshot below:
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.
Please check event on workflow for Bug issue type. It looks like workflow for bug trigger different event than created.
Seba
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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 screenshot with all post functions and validators on create transition?
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.