Basic Rotation allows for a quick configuration of your rotation that will meet most of your general needs of auto-assignment. However, if you would like to configure the rotation for your more specific needs, you could switch to an Advanced rotation by clicking the button on the top right of your screen.
...
.
...
Here’s a list of the fields that you would see on the screen of a Basic Rotation configuration:
Name: While you can name the rotation This can be anything based on your convenience, but we recommend you use a combination of team name, location, etc. so as to clearly identify each rotation, e.g. ‘Telecom Service Team - India - Weekly’
Color: Customization is possible, offering your schedule a unique visibility in Calendar.
Buffer zone: To understand buffer zone much better refer to this page
Time Zone: The time zone is selected automatically based on the user’s profile. But you could search and set another time zone here
Start Date and Start Time: as per requirement
End Date and End Time: as per requirement
Perpetual End Date: Select this option for instances in which end dates are uncertain, or not clearly delineated
Rotation Type: Choose between Fixed Rotation or Distributed RotationRound Robin. Refer to this page for more on Fixed vs Distributed RotationRotation Status: An indicator of whether the rotation is currently enabled or disabled. If you create a rotation but do not want to launch it, or keep the configured item ready as a part of a simulation, simply disable the button.
Please note: A rotation will not be activated even if it is enabled, but the encompassing schedule is marked as disabled
Interval and Interval unit
Duration and Interval unit (Only for Fixed duration): This is the duration (days, hours or minutes) for which the incoming tickets are assigned to one first person in the team (only applicable for a Fixed Rotation).
Please note: If you select the interval unit as minutes, Honcho SARJ allows only multiples of 5 and starts from 60.
Participant and Participant Group:
These include the team members. A project manager has the liberty to select either individual team members or a group of team members (must be configured as a team in your instance). This means, if they want to involve other members beyond the usual team, Honcho allows them to add users for a specific rotation.
Please note:
The ‘Participant' or the ‘Participant Group’ fields are not mandatory on their own. However, one of these two fields must contain values in order to save a rotation.
In the event that the admin selects 1 group and 1 participant, the rotation will include the individual participant in addition to the group members, as long as they are unique.
Rotation Color: The calendar below provides a full view of allotted schedules of team members. Setting a different Rotation color allows you to easily identify the projects/rotations they belong to.
Day/ Week/ Month Calendar View of Rotation Configuration:
The calendar view is a cumulative representation of how the team members are placed in terms of their workload over a time span for various projects they are involved in. The calendar allows you to switch views between a day/week/month. This comes in handy when the Project Manager wants to check if the workload is getting too cumbersome for some team members, and if there is room for task allocation in the case of others. Taking this into consideration, they can then exercise their discretion to distribute the workload evenly.
As you can see, different colors denote different rotations that a team member is a part of.
...
Start Date: The date when your rotation will start
End Date: The date when your rotation will stop
Perpetual Date: Turn this toggle on and you do not want to enter an end date and want the rotation to run indefinitely.
24hrs: Turn this toggle on to run the rotation for 24hrs
Note - If you do not select this, you will have to enter the start time and the end time of the rotation.
Start time and End time: The time window of the day during which the rotation will run.
Team member: The people who will actually be assigned to work on the issues.
Note - These users must have ‘assignable user’ permission in the project.