Skip to end of banner
Go to start of banner

Advanced Rotation configuration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

The Advanced Rotation Configuration view offers extra features and caters to additional criteria like having an option to customize the assignee selection criteria using JQL (Jira Query Language).

Note - If your query is syntactically incorrect, the icon turns red.

Enable Individual Maxcount

Advanced configuration offers a unique feature called ‘Individual MaxCount’, which indicates the maximum number of open tickets that can be assigned to a team member.  This ensures that their daily work doesn’t get cumbersome, and tickets don’t keep piling up unchecked for any team member. Once a team member reaches his Maxcount, they are not auto-assigned any more tickets until they resolve one of their open tickets. The incoming tickets are distributed to the other team members in either a fixed or a distributed pattern. If all team members reach their Maxcount, then all the incoming tickets are placed in the pool, which can be viewed in the Pool Dashboard section.

Let us assume a team with two members - A and B, in a Distributed Rotation pattern. A is a junior member with a Maxcount of 5, and B is the senior member who can handle a Maxcount of 8. For the first 10 incoming tickets, A and B will get 5 tickets each (one at a time). However, the 11th ticket will be auto-assigned to B, as A has reached its Maxcount criteria. B will continue to get the 12th and the 13th ticket as well. The 14th ticket will be reserved in the pool with an unassigned status (assuming all the previous 13 tickets are open).

As soon as either A or B mark one of their tickets as ‘Done’, the tickets reserved in the pool will get assigned to them on a first-in-first-out basis.

  • No labels