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 current behaviour of Round Robin assignment seems bit odd.
For example, I've a team of 6 members(A,B,C,D,E,F). Now Monday I get 3 tickets, so it get assigned to A,B and C.
Now, when Tuesday starts, 2 tickets comes in and it should get assigned to D and E but it will get assigned to A and B again.
I would like to continue the round robin not based on a day but based on the user list. So, if A,B and C are assigned tickets on 1st day and when next ticket comes it should go to D, E and F and the cycle should repeat to A and so on.
Let me know if this is possible to setup.
Here is the screenshot of the rule I am using
@APREMKU6 - Have you tried creating a group in the admin portal, adding your users into the group and then setting the round robin on the group instead of a user list?
I know it shouldn't make a difference but might be worth trying.
Let me try that as well. But I am not sure whether I've access to create a group but I will see to get one created and try it.
Thanks @Marcus Jones
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @APREMKU6 ,
I would second @Stephen Wright _Elabor8_ 's answer. Round robin's scenario would be good when you have a heavy inflow of tickets. "Balanced Workload" would be a better suited for your use case here.
Although I found a few articles that mentioned the Round Robin working, and it should work the way you want it to in the description:
Would Suggest raising a support ticket in case with Atlassian if this hampers your working : https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @APREMKU6
Not the answer you might be hoping for - but if you have so little tickets being received, is round-robin the best approach?
Perhaps balanced workload would be better?
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Stephen Wright _Elabor8_and @Jehan Bhathena I will look into the balanced workload, But there are internal tasks or Adhoc requests which gets raised and that is something which I can assign based on workload.
But just for the customer issues we want to make sure everyone gets a hands on to it by getting a ticket to work.
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.