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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm having trouble figuring out how to use automation to select a random issue in the backlog. Here's what I'd like the automation to complete, weekly (say Mondays at 9 am):
Select one random backlog issue with a priority of Minor, then transition that issue to In Progress while assigning it to a specific user.
Has anyone done something like this? I can't figure out how to accomplish it with the automation rules.
Hi @Eric Spiegel welcome to the Atlassian Community!
Why would you want to automate that?
Example: 2 backlog issues with the same priority still can have a very different estimation (hours or story points) or ranking.
Backlog grooming and sprint planning are a team process.
And if you working kanban, then items should be pulled from the backlog, not pushed.
This is for a Jira board that only I use. I want to do that to help me chip away at wishlist tasks and helps me avoid decision paralysis when picking what to work on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just pick the first one on your list if you don't care about the rest 😁
I do better understand your question for automation now 😉
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's kind of like the Netflix problem. So many things to do, but nothing to do.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, and...I agree with Dave: pick the first one and just do it :^)
If you really, really...want the item to be a surprise/random one, you could probably write a rule using the Lookup Issues action, the random() and other math functions, select an item with get(), and then start it. Doing this, you would learn a bit about automation rules, but probably not reduce the size of your backlog any.
Kind regards,
Bill
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.