Expert Finder

  • Any user can explore the skill tree, viewing skill hierarchy and the qualified experts

  • Users can search for 1 or more skills to to find experts with the required skill set

  • Users can inspect experts’s skill sets

  • Users can identify skill gaps by comparing expert’s skill set with another user, group or any set of skills

Skillset Field

  • By creating Skillset fields you can add skill requirements to tasks. You can model complex cases (such as separate requirements for Engineering and Business SMEs) by creating multiple fields

  • Admin can customize skill tree per field type (e.g. separate skill trees for Engineering and Business experts)

  • Users see the list of experts matching the skill requirements right on the issue screen

  • Users can query issues by skill requirements or by matching experts

  • Customers can restrict transitions to experts only


Risk Analysis

  • Authorized users can analyze any set of tickets and see:

    • Skill sets in demand and their Scarcity (Blocker (no experts), Bottleneck (1 expert), Scarce (2-3 experts) or OK)

    • Users are Bottlenecks or hold Scarce skills

    • Issues that are at risk due to skill scarcity

    • Skills for Jira quantifies demand in # of tickets, hours or Story Points if configured by the admin

You can read more about Skills for Jira analytics here: https://totem-dev.atlassian.net/wiki/spaces/SFJDC/pages/479592874

Self-service Assignments

  • Customer can configure multiple work queues for their users to pull tasks from

    • Admin uses JQL or selects one of the existing filters to flexibly define the task scope and order in the queue

    • Tasks can be pre-assigned to not be pulled by anyone aside from the specified person

    • Dependency links can be configured, to skip tasks that depend on other tasks that are not yet completed

    • Admin can limit work in progress per queue (e.g. max 1 task or don't allow pulling while tasks in progress have more than Xh remaining time)

  • Admin can hide the work queue from their users to avoid bias and encourage pulling

  • Customer can add a "Get next task" button widget to their existing Jira dashboard

  • Users get a dedicated Assignments dashboard where they can:

    • Pull their next most imporatnt task that they are qualified for

    • See their tasks in progress

    • See their work queue (when enabled by Admin)

    • See the skill sets required by the tasks in the current queue. Skills for Jira highlights the skills that the current user lacks

    • See the other qualified experts

You can read more about self-service assignments here: https://totem-dev.atlassian.net/wiki/spaces/SFJDC/pages/479592708


  • Authorized users can simulate what happens if the specified set of users (all by default) pull tasks from their work queue as soon as they are available (based on the time estimates of the existing tasks and Assignments configuration)

  • User will see performance stats forecast as well improvement opportunities

    • Users utilization (out of user's total capacity (8h * (project end - project start)), how many hours were they working on tasks)

    • User utilization over time (chart)

    • Skill sets utilization

    • Skill set utilization over time (chart)

    • Delays (issues delayed due to temporary no experts)

    • Blocked (issues not progressing due to no experts)

    • Throttling (skill sets that throttle your project)

  • Recommendations:

    • Ideal combination of skill sets that would maximize the delivery efficiency?

    • Adding people with which skill sets would help increase the speed the most?

  • Experiments (allow making "changes" to the composition and re-run simulation):

    • Adding virtual people with recommended skill sets, removing people


  • Inspect each user’s personal work queue (i.e. the ordered list of tasks, first of which will be assigned to the user upon pressing the “Get next task” button)

  • View the same tasks that the user sees in their https://totem-dev.atlassian.net/wiki/spaces/SFJDC/pages/479592708 Dashboard

  • View tasks that are hidden from the user due to queue configuration

  • View skill gaps that prevent user from pulling tasks from their assigned work queues