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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Automate moving issues from the backlog to the ready status

Sean Aguilar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 22, 2023

I have a backlog and my first status after backlog is ready. I want to run an automation that counts the number of issues in my ready status, and if its less than 5 then I want to move issues from backlog to ready until there are 5 issues in ready. I want to move them out of the backlog in rank order.

How would I go about this? Thanks in advance.

1 answer

1 vote
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.
Sep 23, 2023

Hi @Sean Aguilar -- Welcome to the Atlassian Community!

I assume your team is using Kanban practices and a Jira Kanban board.  What you describe is often called Queue Replenishment, and I suggest learning more about the manual / people steps involved in that practice before automating it as doing so may remove some of the benefits.

Back to your question...

What you describe is possible, and you could do this with an automation rule with:

  • a scheduled trigger,
  • a lookup issues action to check the number of issues in "Ready",
  • a condition to check the lookup before proceeding,
  • another lookup issues to gather backlog issues with ORDER BY Rank ASC, and
  • finally a loop (or single operation) to transition one/or more issues.

The tricky part will be pulling the correct number of issues in one rule, which can be done with variables and advanced branching.  A simpler approach would be to only pull in one issue at a time and have the rule run more frequently.  (I would recommend against that as the packaging model is changing for automation rules.)

To get you started on creating your rule, please refer to these documentation and example sources: 

And if you run into problems creating your rule, please post images of your complete rule, the audit log details showing the execution, and explain what does not work as expected.  Those things will provide context for the community to help.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events