Before the team can we start using Self-service or Automated assignments, an Administrator needs to configure the work queues and enable Pull support configuring Self-Service Assignments, let’s briefly talk about what happens under the hood when a user requests their next task by pushing the “Get next task” button either in User Console / Assignments or in a Jira Dashboard Widget.
Step #1
Task selection starts by identifying all work queues available to the user. If the “Default Queue” is enabled, it is available for all users to pull from. Any other queue
Step #2
In order to select the next most important task, Skills for Jira compares Top 1 tasks from each of the work queues available to the user using the following rules:
Higher priority tasks always go first
Given the same task priority, tasks from higher-priority queues go second
Given the same task priority and queue priority, the work queue is selected at random
Step #3
Skills for Jira will update the Assignee field to the current user
Step #4
The assigned task will be transitioned to one of the statuses specified in the queue configuration as “In Progress”
Work Queue configuration
Administrator needs to enable Self-Service Assignments and configure the work queues in Skills for Jira - Administration Console / Assignments.:
...
Creating Work Queues
Skills for Jira ships with a “Default Queue” that applies for every user in Jira. Administrator can define any number of additional Queues to model assignment scenarios of any complexity. Queues can represent tasks of a specific Team, or Product, or Sprint, or any other scope of work.
The additional queues created by Administrator can be restricted to specific user groups:
...
| Info |
|---|
Only users that are both in “marketers” and “trainees” groups will get tasks from “Marketing Training Queue” |
Configuring Work Queues
Scope (JQL
...
)
, controlling the scope of work, task order (through the scope JQL filter), visibility, as well as control max user workload.
Info
“Scope (JQL filter)” defines the scope and order of the tasks in the work queue. The “Get next task” button will assign the best task from across all relevant work queues, using the following rules:
Higher priority tasks from across queues always go first
Tasks from higher-priority queues go second
The work queue is selected randomly between same-priority work queues
Scope is defined in the form of a JQL query: you can select one of the existing filters or specify JQL directly on the configuration screen.
| Info |
|---|
Tasks from the new queue will be fetched in the order defined by the scope’s “ORDER BY” clause |