On this page
Create sub-tasks and link them to the parent or current issue that has a specific priority of your choice.
Configuration steps
Add a Create issue post function to the desired workflow transition.
Issue type*
Choose selected issue type and sub-task as its value.
Parent issue*
Choose current issue.
Summary*
"Type in an appropriate summary for the issue you are creating."
Fields
Issue links
Select is blocked by (Blocks)Issues to be linked*
This will show up in the popup window.
Choose current issue.
Condition
Insert the following expression:
%{issue.priority} = "Insert your desired priority here"
For more information about this feature, visit the following page.
Run as*
Choose which user* will be able to execute the post function. By default, it is set to the Current user.
Related examples
| Use case | Type | Function | Use case description | Complexity |
|---|---|---|---|---|
| Automating Annual Access Review for Company Software in Assets | For the annual access review of applications used in the company and managed as Jira Service Management Assets, we want to create a dedicated task for each application owner to review the people who have access to the application they are responsible for. | INTERMEDIATE | ||
| Create an issue in the current project | Create an issue in the current project and additionally set a summary. This use case comes in handy if you quickly need to create i.e. a new bug which relates to the current issue | BEGINNER | ||
| Create an issue with a summary to check for attachment type | Creating many issues and adding a summary and a description can be a bit frustrating and time-consuming. To avoid such things, the following use case shows you how to create a sub-task with a summary to check for attachment type in the parent issue. | INTERMEDIATE | ||
| Create a simple sub-task | Create a sub-task, set the summary based on the parent's component, and set the assignee to the current user. | BEGINNER | ||
| Create a story in an Epic | Link your Epic each time you create a story. | BEGINNER | ||
| Create a sub-task for each component | Create a sub-task for each selected component in the current issue. | BEGINNER | ||
| Create a sub-task for each user selected in a User Picker field | Create automatically a sub-task for each selected user in a User Picker (multiple users) field of the transitioned issue. | BEGINNER | ||
| Create a sub-task for high priority issues | Create a sub-task only if the priority of the current issue is "High". | INTERMEDIATE | ||
| Create a sub-task linked to issues with a specific priority | Create sub-tasks and link them to the parent or current issue that has a specific priority of your choice. | INTERMEDIATE | ||
| Create a sub-task mentioning the assignee when a high priority task is ready for review | Keep your team on track and up to date by creating a sub-task mentioning the assignee's full name and with issue links linked to the appropriate issue whenever a high priority issue has been moved to the status "Review" | BEGINNER | ||
| Create multiple sub-tasks with different summaries and descriptions | Create multiple sub-tasks with different summaries and descriptions. | INTERMEDIATE | ||
| Create two sub-tasks when a user story is being approved | When a story is approved, two sub-tasks for Development and QA will be created. | INTERMEDIATE |
If you still have questions, feel free to refer to our support team.
