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
...
Info |
---|
Tasks from the new queue will be fetched in the order defined by the scope’s “ORDER BY” clause |
Local Priority
By default, when making the “which queue to pull from next” decision, Skills for Jira picks the issue with the highest priority, only reverting to queue priority (i.e. “1st pick”/”Last pick”) when issues are equal.
With Local Priority set, priorities of issues in this queue become irrelevant outside of the queue context. High priority tasks will not take precedence over tasks from other queues.
By enabling “Local Priority” on your queues you can ensure that issues from more important queues are delivered first, regardless of the priority of the tasks inside.
...
Info |
---|
Figuring out how a queue with “Local priority” will interact with other queues can be challenging. Here a a few examples to help you assess fit for your use case:
|
Statuses
You define how a task will be transitioned on assignment by selecting a set of FROM and TO statuses
...