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,556,301
Community Members
 
Community Events
184
Community Groups

Automation & Round-Robin

Edited

Hello,

An user has created an Automation involving "Round-Robin assignee method". The automation is working fine . . . but

- How do we know or retrieve the next assignee's name at any given time?

In any automation system, the next value to be used is stored into a file and it can be retrieved by calling a  "variable". How does this work in Jira? Does Jira have such type variable's name?

M

2 answers

@Rilwan Ahmed thank you for your reply but you have just described how Round-Robin works.

In IT Data Stack there is the concept of FIFO - First In First Out a way to manipulate a Data Structure in a sequential way. In FIFO you know which one was the last manipulated variable and which one will be manipulated next.

Round-Robin as used in this case is nothing more than a FIFO where the last manipulated variable is re-queued.

For example should I edit the Round-Robin Automation, not touching the IDs, will the sequence restarted? I bet it is! This is not an ideal situation if you have 10 - 20 or 50 of those ID that MUST be dealt in sequence.

I would like to know whether there is way to "call" such variable and retrieve the last value used.

0 votes
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 24, 2022

Hi @Mario Coluzzi ,

When you create the automation with round robin assignment, you need to provide the list if users. The rule will assign issues to users one after the other in the given sequence. Once it reaches the last member of the group it will start again from the beginning.

So to identify who is the next assignee, you need to know the last ticket assignee. 

@Rilwan Ahmed ,


I have the same doubt, considering that I know who is the last one, how to find out the next one?


Imagine I have 10 guys in my team and the queue is running for days, I don't want to lose track and to be clear who is next on deck, so Imagine that A jira is just assigned to someone in a round-robin fashion, at that moment I would like to send an email/slack message, saying hey the jira was created the assignee is XXX and the NEXT one in queue/deck is XXXX!


There is a smart/value or anything I can type that will show me the value of the next one in queue?


I cannot use the last assigned issue because the round-robin assignment only works (IF) during business hours, so if we had jira created outside that time it would have assigned the oncall ALSO the names under round-robin list get edited if someone is on sickleave or holiday, so looking to the last one assigned would not capture that as well.

Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 25, 2022

Hi @Mario Coluzzi 

I am not aware of any smart values to show next assignee. But when you create the automation rule, you need to give the list of assignees. Jira will be taking assignee in that given order. 

So if you have the list, you will know the next assignee. 

 

image.png

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events