Assignment Rules

The Assignment Rules page in SnapAssign provides an overview of all the assignment rules configured for each team. This page allows administrators to manage and organize the rules that determine how issues are assigned to team members based on various criteria such as source, method, and shifts.

Page Overview

• The page lists all teams, with the ability to expand each team to view their specific assignment rules.

• Each team has a set of assignment rules that define how issues are distributed to its members.

• The rules are organized in a table format with the following columns:

  • Name: The name of the assignment rule.

  • Source: The source of issues that the rule applies to (e.g., projects, all issues).

  • Method: The method used for assignment, such as Load Based or Round Robin.

  • Shift: The working hours or shifts during which the rule applies. Shifts are labeled with color-coded lozenges for easy identification.

Open

Assignment rule list

Key Features

• Team Expansion and Collapse:

  • You can expand or collapse each team's section by clicking on the team name to display or hide its assignment rules.

  • This feature helps users manage multiple teams efficiently on the same page without overwhelming the interface.
    
    

    Open

    

    Team expansion and collapse

• Assignment Rule Details:

  • Each rule displays the following information:

    • Name: The unique name of the rule.

    • Source: The origin of the issues to be assigned (e.g., projects, all issues).

    • Method: The assignment method used (e.g., Load Based, Round Robin).

    • Shift: The working hours or shifts during which the rule applies, such as 08:00 - 15:59 Shift, 16:00 - 23:59 Shift, 00:00 - 07:59:00 Shift. These shifts are color-coded for clarity.
      
      

  Open

  

  Assignment rule details; Source
  Open

  

  Assignment rule details; Shift

• Default Assignment Rule:

  • Each team has a Default Assignment rule, which acts as a fallback to ensure that all issues are assigned, even if they don't meet the conditions of the other rules.

  • The Default Assignment rule applies to All Issues and typically uses a Round Robin or Load Based method with the Default 24/7 Calendar for all team members.

  • This rule cannot be deleted but can be edited to adjust the team members and calendar.
    
    

    Open

    

    Default assignment rule

• Search Functionality:

  • At the top of the page, there is a Search bar that allows users to quickly find specific rules or teams by entering keywords.
    
    

    Open

    

    Assignment rule searching

• Add New Rule:

  • The + Assignment Rule button at the top right allows administrators to create a new assignment rule for a selected team.

    1. Select a team to create the assignment rule for.

    2. Provide a name for the rule and select source projects.

    3. Click "+ More" to refine the source with additional criteria like:

       • Status: Filter issues by their current status.

       • Issue Type: Specify types such as Task, Bug, Story.

       • Issue Priority: Set priority levels for issues.

       • Issue Filter: Utilize existing filters shared by the organization.

       • JQL: Advanced filtering using JQL (Jira Query Language).

    4. Proceed to the Method section.

       • Round Robin: Issues are assigned in a round-robin fashion.

       • Load Based: Assign based on the load (by count of assigned issues or by the sum value of a selected field).

    5. Click "Next" to proceed to the Shift section.

       • Shifts: Define shift names, calendars, and assignable team members.

    6. Click "Save" to create the rule.
       
       

  Open

  

  Creating an assignment rule - I
  Open

  

  Creating an assignment rule - II
  Open

  

  Creating an assignment rule - III

Understanding the Assignment Methods

Open

• Load Based: The Load Based method dynamically assigns issues based on the current workload of team members. The system evaluates the distribution of tasks and assigns the next issue to the team member with the least workload. This ensures a balanced allocation and prevents overloading any individual.
  
  Methods:

  • by count of assigned issues:
    In this approach, issues are assigned based on the number of open tasks already allocated to each team member. The system assigns the next issue to the user with the fewest currently assigned tasks. This method is useful for maintaining an even task distribution without considering the complexity or effort required for each issue.
    
    

    Open

    

    Method by count of assigned issues

     

  • by the sum of value of a selected field:
    Instead of simply counting issues, this method assigns tasks based on the total workload value accumulated from a specific field (e.g., Story Points, Estimated Hours, or any numerical custom field). The next issue is assigned to the team member with the lowest total sum in the selected field, ensuring a fair distribution of workload intensity rather than just issue count.
    
    

    Open

    

    Method by the sum of value of a selected field

     

  • by the sum of value of a selected dropdown field:
    This method works similarly to the previous one but applies to a dropdown field where different values have predefined weights or priorities. Issues are assigned based on the sum of these values, ensuring that workload is distributed fairly while considering specific categorization factors (e.g., priority levels, effort estimations).
    
    

    Open

    

    Method by the sum of value of a selected dropdown field - I
    
    
    Open

    

    Method by the sum of value of a selected dropdown field - II

    
    
    

• Round Robin: The Round Robin method assigns issues to team members in a cyclic order. Each new issue is assigned to the next available team member in a predefined sequence, ensuring an even distribution of tasks over time. This method does not consider workload or task complexity—each member receives an equal number of issues regardless of difficulty.
  
  

  Open

  

  Round robin