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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Sandip Bhosale -- Welcome to the Atlassian Community!
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
What problem are you trying to solve with this rule? That is, what does it do and why do you need it? Knowing those things will help the community offer better suggestions.
The symptom you describe seems to indicate the rule has incorrect conditional logic, possibly using a basic condition when you wanted to use an if/else structure. Seeing the rule will help to confirm that.
You describe wanting the action of adding the comment on issue transition to another status, but the rule is triggered on a scheduled trigger.
Have you considered using the Issue Transitioned trigger instead? Or are you instead wanting this rule to trigger when a transition has not occurred?
Please post images for both rules showing the audit log details, showing the rule execution when it did not work as you expected. Those will provide context for which issues were processed and the actions taken.
Also, it appears you have changed the rule actors from Automation for Jira to Jira Administrator. Why was that change made? Changing the rule actor can cause actions to not work / fail when the actor does not have the necessary permissions.