Features used to implement the example
- Create issues and sub-tasks
Example: Create a dynamic set of sub-tasks based on checkbox selection with unique summaries
In this example, multiple sub-tasks with unique summaries are added to an issue on issue creation based on the options selected in a custom checkboxes field "Additional issues". Whenever one of the options Newsletter, Release Notes or Documentation is selected, the corresponding sub-task will be created with the correct "Fixed Version" added to the summary of each sub-task.
The configuration will look like this:
As the number of sub-tasks should be dependant on the option selection, the Issues to be created option is set to String List with the value: toStringList(%{10200})
Note that
- %{10200} is the field code for the "Additional options" custom field (this field code might differ on your instance)
The dynamic summaries are parsed with the following expression:
getMatchingValue(^%,["Newsletter","Release Notes","Documentation"], ["Newsletter for Version " + %{00074}, "Release Notes for Version " + %{00074}, "Documentation for Version " + %{00074}])
Note that:
- %{00074} is the field code for "Fix Version/s"
Since this behaviour should only occur with release issues, the following Conditional execution is added: %{00014} = "Release"
Once configured the transition will look like this:
See Result screenshots post-function "Create multiple subtasks based on options checked in a checkbox".
Other examples of that function
- Assign new issues to a different project role depending on field value in current issue
- Clone an issue and all its subtasks (with additional restrictions)
- Create 3 issues in 3 different projects
- Create a dynamic set of sub-tasks based on checkbox selection with unique summaries
- Create a static set of sub-tasks with unique summaries
- Create a story for each component in an epic
- Create a sub-task for each user selected in a Multi-User Picker
- Create a sub-task in each story of an epic
- Create specific sub-tasks for each selected component
Related Usage Examples
-
Create a dynamic set of sub-tasks based on checkbox selection with unique summaries (Jira Workflow Toolbox (Server / DC) 2.x)
-
Add and remove a single or a set of items from multi valued fields (Jira Workflow Toolbox (Server / DC) 2.x)
-
Add all assignees of certain sub-task types to a "Multi-User Picker" custom field (Jira Workflow Toolbox (Server / DC) 2.x)
-
Update Cascading Select custom field with a value of the field in parent issue (Jira Workflow Toolbox (Server / DC) 2.x)
-
Create a sub-task for each user selected in a Multi-User Picker (Jira Workflow Toolbox (Server / DC) 2.x)
-
Validation on sibling sub-tasks depending on issue type and status (Jira Workflow Toolbox (Server / DC) 2.x)
-
Block a transition until all sub-tasks have certains fields populated (Jira Workflow Toolbox (Server / DC) 2.x)
-
Restrict sub-task type creation depending on parent issue status (Jira Workflow Toolbox (Server / DC) 2.x)
-
Require at least one sub-task in status "Resolved" or "Closed" when "Testing required" is selected in Check-Box custom field (Jira Workflow Toolbox (Server / DC) 2.x)
-
Restrict sub-task type creation depending on parent issue type (Jira Workflow Toolbox (Server / DC) 2.x)
-
Transition sub-tasks when parent is transitioned (Jira Workflow Toolbox (Server / DC) 2.x)
-
Transition only a sub-task among several ones (Jira Workflow Toolbox (Server / DC) 2.x)
-
Moving sub-tasks to "Open" status when parent issue moves to "In Progress" (Jira Workflow Toolbox (Server / DC) 2.x)
-
Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status (Jira Workflow Toolbox (Server / DC) 2.x)
-
Automatically close resolved sub-tasks when parent issue is closed (Jira Workflow Toolbox (Server / DC) 2.x)