Assign Issue to Project Role Using Algorithm

Owned by Werare Support User
Last updated: Nov 26, 2023
3 min read

This post function assigns the issue to a user holding the specified role in the project according to the selected algorithm an criteria. It also offers the flexibility to control its execution based on preconditions. By utilizing preconditions, you can determine whether the post function should be executed or skipped based on the evaluation of a Jira Expression. The precondition, defined in terms of a Jira Expression, should return a boolean value. If the result of the precondition is true, indicating that the specified condition is met, the post function will be executed. Conversely, if the precondition evaluates to false, the post function will be bypassed, allowing for conditional execution based on your specific criteria.

 

As “Issues to Operate on” , you can select one of the:

  1. Current Issue: The current issue being transitioned

  2. Sub-tasks of Current Issue: The sub-tasks of the current issue.

  3. Parent Issue of Current Sub-task: The parent issue of the current sub-task.

  4. Issues that Belong to Current Issue: All the stories that belong to the current epic.

  5. Epic of Current Issue: The epic issue associated with the current issue.

  6. Issues Linked to Issue with Any Link Type: The issues linked to the current issue using any link type.

  7. Issues Linked to Issue with Following Link Type: The issues linked to the current issue using a specific link type. You will be asked to provide the link type.

  8. Issues returned by JQL: The issues returned by a JQL. You need to provide a Jira Expression whose result will be used as the JQL to find the issues. You can also provide a static string in double quotes if you prefer a static JQL.

Dynamic JQL Query Example. issue?.key will be replaced by the key of the issue transitioned. The result will be “Epic Link” in (SCRUM-14) if the issue transitioned has the key SCRUM-14.

 

Static JQL Query Example

As algorithm/strategy, you can select one of:

  • Balanced Workload: This option ensures a balanced progression of the number of assigned issues among the children of the selected user. In this option, you will encounter four additional choices that indicate the type of balancing you will perform.

    • Number of Open Issues in Project: Assigns users based on the number of issues they have in the selected project.

    • Number of Open Issues in Jira: Assigns users based on the number of issues they have in the Jira.

    • Total Story Points of Open Issues in Project: Assigns users based on the total story points of the issues in the project.

    • Total Story Points of Open Issues in Jira: Assigns users based on the total story points of the issues in Jira.

  • Random: This option randomly assigns the issues to the children of the selected user without any specific balance or ordering. In this case, there is no consideration for maintaining balance or any specific sequence.

  • Round Robin: This option assigns the issues to the children of the selected user sequentially. This means that each time, the next user in line will be assigned the issue.