Before we start 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.
...
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
...
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.
| Note |
|---|
Scope MUST include ALL issues that belong to the queue. This includes both tasks that are waiting to be assigned as well as the ones that are already in progress |
...
| Info |
|---|
Tasks from the new queue will be fetched in the order defined by the scope’s “ORDER BY” clause |
Statuses
You define how a task will be transitioned on assignment by selecting a set of FROM and TO statuses
...
Tasks in any of the “In queue” statuses represent the actual queue. They become available for fetching using the “Get next task” button.
When the task is fetched, it is transitioned into one of the “In progress” statuses for which the transition exists in the issue-specific workflow.
Qualification
Here you select one of the Skillset fields that specify skill requirements for tasks in the queue:
...
Tasks that include skill requirements that do not match the current user’s skill set do not appear in their work queues and are not available for pulling.
Pre-assigned user
Normally tasks can be pulled by any user that has the necessary skill set. Sometimes, however, you may want to pre-assign a task to a specific person.
While the recommended approach is to identify and document the skill or knowledge that makes this person the best candidate for the job, in order to be able to document or transfer it, in real work scenarios, it’s not always feasible.
You can use a separate field that will specify the preassigned user. This way, if the field is set, the task will only be available for pulling by this specific person.
| Info |
|---|
Only User Picker (single user) fields can be used as “Pre-assigned user” |
Dependencies
Very often a task can only be started after the ground work is done in previous tasks. Jira has a built-in concept of issue linking where you can define such dependencies as well as various other relations between tasks.
By indicating these dependencies in work queue configuration you will ensure that a task will not appear in the queue and will not be assigned until all dependencies are resolved.
...