Users can reach the configuration page from the section shown in the picture. By clicking the button (1) users will go to the screen that is given below.
On that page, users can add absent users, alternate assignees and dates which controls the auto assignee function for the absent users. Let’s assume user Tanya is absent on dates between 16/05/2022 - 18/05/2020 and as defined before David will take care of her issues which means issues are assignable to David automatically.
TOM also has a JQL function called currentlyOffTime() which shows all the issues which are assigned to the absent user. On the right middle of the page, users are able to see the related information about the auto-assignment rules and by clicking “Assign to alternate assignee” it is possible to assign the issue till the end time is up!
In Project Rules section, users are able to add assignment rules for each project separately.
In Global Rules section, users are able to reach the rules that is defined before from the Manage Apps section.
By simply clicking the button called Assignment Rules (1), users can easily reach the Global Assignment Rules configuration page. After that, just click the plus sign (2) on right top of the page and now you are ready to add a rule. You can also edit and delete the rules that you created before(3).
While adding an assignment rule, users have to choose rule name, assignee, assignment strategy and no assignment scenario. It is also possible to add JQL to the rule.
In Edit Assignment Rule page there are some fields that you need to understand well which are,
“Project Scope” users can choose single project, multiple projects or global(global means ALL projects) for the rule that user wants to implement it.
“Assignment Strategy” users can make a selection between Round Robin or Random. Let’s assume that we defined more than one assignee, round robin represents that, while implementing the rule assignees will be selected respectively instead of the absent user and random represents that, user will be selected randomly between the assignees.
“No Assignment Scenario” consists of Alternate Assignee, Unassign and Do Not Reassign. Let’s assume there are two users(User A, User B) which are considered as assignee in the Add Assignment Rule screen and a random issue is assigned to User A. However User A is absent. On the other hand, User A had defined a rule for himself before from the admin section configuration page which is(If User A is absent, alternate user will be User B). Then, that predefined rule will be working instead of this rule. Unassign means if the selected assignee is absent then the issues that are assigned to that user will be automatically set as unassign. Do Not Reassign means, nothing will change if the selected user is absent. The issues that are assigned to absent user will remain same and assignee will still be the same user.
There are two post functions that users can add to any transition as seen in the figure. First post function (Assign By Rule) does that , assign users according to assignment rules(Global Rules and Project Rules) which matches with the appropriate issue that is defined before. Second post function (Assign To Alternate User) does that, assign to alternate user when a user is currently unavailable.