Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,953
Community Members
 
Community Events
176
Community Groups

Rule tries to run action twice per trigger. Why? (When assigned, transition issue)

Edited

I'm working in Jira Server, using Automation for Jira Lite to create what should be a very simple rule: 

  • When issue assigned
    • transition the issue status to In Progress

However, when I assign an issue, the audit log indicates that it tries to transition the issue twice. Why is this happening? 

Detailed Behavior:

At first, the rule was just two components, the trigger and the action. It would return two status entries. First:

Success. Transitioned issues to In Progress

Then the second status: 

No matching transitions could be found for issues (with current status):
IDX-2 (In Progress - 3)
Apparently, it's reporting an error because it can't find a transition from "In Progress" to "In Progress" when it attempts to run the transition a second time. 
Screen shot with example of these back-to-back log entries.
image.png
To verify it really is trying to run the action twice, I added a condition: only run the transition if the starting status is "To Do."
Now it returns two statuses again. First it transitions the status successfully, like before. The second status is no longer an error--it just reports doing nothing, since the criteria to run the action wasn't met when it tries to run a second time.
image.png
Stuff I have already checked: 
  • I get the same result regardless of whether I create this action by "Selecting the Destination" or "Selecting the Transition"
  • There is only one transition that leads to the status.
  • I have removed all conditions from the transition. It doesn't have any validators. It doesn't even do any Post actions except the defaults. 
  • Admins, Devs, and Users currently all have permission to transition issues, to assign issues, and to be assignees.
  • I am a global Admin and project Admin, I own the rule, and I am currently set as the actor for the rule. 
While I could in theory leave it "functioning" like this, I'm not happy leaving an unexplained behavior in my production. So what is going on here? Why is it running twice? 
(Edited for typos)

1 answer

1 accepted

2 votes
Answer accepted
Pramodh M Community Leader Jan 21, 2022

Hi @Alex Sticco 

Can you change the actor to one who has the permission to transition the issue and let me know if it returns the same result

Thanks,

Pramodh

I changed the actor to our other admin. (To be clear, I do have permission to transition the issue myself, but I assume you meant change it to a different person who also has that permission.)

To my surprise, changing the actor has resolved the problem! 

Thank you!...But also...WHY? Can you explain what caused the problem and why this fixed it? I do not have this problem on any other rule where I left myself as the actor. 

Like JT Olmstead likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events