Understanding Max Load/ Busy Status / Busy JQL

We understand that if your team members are already working on some items, it might be tough for them to be able to sort through a long list of tasks that they are assigned to. That is the reason we introduced the concept of Max load in advanced rotation.

Here you can specify the total number of tickets your team members can work on in parallel. Once they hit that number, any new issue that comes in will go to Pool or be assigned to a different team member.

You can also see the current load of your team member next to the maximum limit.

To make this more easy to configure, we have also added the option of - Busy Type.
Here you can select Basic, and in turn select which workflow statuses you want to consider to busy. example, you might want to consider only the issues in ‘Work in Progress’ status as busy.

OR you can play around with the custom configuration of what means to be ‘busy’ for your team members and define a JQL instead.
Cool, right?