You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
the image you provided is not helpful. I assume you are testing by creating a new issue in the project where this rule exists? when you do that please view the associated log and share the details.
I dont understand "It works fine when it is triggered manually, but doesn't update when it is automated."
this rule should trigger whenever an issue is created. it isn't a manual rule.
i need to see the audit log associated with an issue being created. if the rule does not trigger at all when an issue is created then either...
On Aug 10 you replied to Melo with an image of the audit log but it was only for the config change. The point is that The audit log is in that very place where you took that image.
project settings > automation > audit log
find the entry that is associated with the create issue event. It may show success or failure. Click on show more and share the results.
Ok. For the project associated with these issues please go to the following location and give me the screenshot. Project settings > Automation
I want to see the list of rules for that project and please indicate which rule is in question here. Similar to below.
Also, if you're not planning to trigger this rule in multiple events, you can choose the trigger "Issue Created" instead of "Multiple events">"Issue Created"
Hi Shilpa, that's strange.
Here are some tips for debugging your rule
Also, some information about service limits, but I guess that shouldn't be the case
You can check how many executions you had - I think some cloud subscriptions may have limitations
I'm not sure if I will be able to help further, if the scope is fine, and if you're creating issues and the rule is not being triggered being triggered. I would suggest opening a ticket with Atlassian support.