Add sub-tasks to issue on creation

Often creating repetitive issues is daily work, e.g. in a software development release process. It might be that for every new feature specific tasks have to be done in order to successfully release a new software version containing this feature, be it updating the product documentation, the marketplace presence or sending a newsletter to all customers.

To avoid creating these issues always manually, the following automation rule can easily manage this by creating the issues automatically.

Should I use an automation rule or a workflow post function?

When to use this automation rule and when to use a workflow post function?

This use case is very useful, if repetitive issues have to be created in several projects that have different workflows. Configuring just one automation rule might then be the easier way to go. But if this scenario is only necessary for one project and workflow, the Create issue post function would make more sense. In this case you might want to check out our corresponding post function use case.

Need issue creation based on a custom field?

No problem! Just take a look at this use case!

Issue Created event

Create a new rule and name it appropriately.

Providing a description will help you to identify what the rule does but this step is optional.

Add a Trigger → Issue Event → Issue Created

Boolean condition

Add the Boolean condition and enter the following Parser Expression*

%{trigger.issue.project.key} in ["key1", "key2", "key3"] and %{trigger.issue.issueType} = "New Feature"

Replace key1, key2 and key3 with your project keys.

Create Issue action

Issues to be created*

Choose Multiple issues

Parser Expression*

Type 3 and change the parsing mode to Date/Mathematical

Issue type*

Choose Sub-task

Parent issue*

Choose Trigger issue

Summary*

Use the following Parser Expression

getMatchingValue(^,[1,2,3],
["Documentation","Marketplace","Newsletter"])

Description*

Use the following Parser Expression

getMatchingValue(^,[1,2,3],
["Issue for creating the documentation for the feature",
"Issue for updating the marketplace presence for the app",
"Issue for creating a newsletter for the feature"])

Error rendering macro 'excerpt-include'

No link could be created for 'DECADIS:Automation Use Case - Activate Rule Step'.

Screencast

This is how the configuration above should look on your screen

Related examples

Use case	Type	Function	Use case description	Complexity
Add comment after seven days in the same status
Add components of the epic to the current issue
Add links to the issues in a ScriptRunner Issue Picker field
Add sub-tasks to an automatically created issue
Add sub-tasks to an issue on creation
Assign an issue to the last assignee on a transition
Assign issues to your team during a transition
Automatically assign issues to your team
Automatically close parent when all sub-tasks are done
Automatically close sub-tasks when parent is completed
Bulk clear the issue resolution
Bulk edit the issue resolution
Close epic when stories are done
Close stories when epic is done
Copy excerpted value from new comments
Copy the parent issue comments to its sub-tasks
Create issue link when issue is created
Create sub-tasks depending on selected values in a custom field
Delete the attachments of an issue 30 days after closing it
Inherit value from parent in Advanced Roadmaps hierarchy
Keep calculated custom field in sync
Keep the priority of parents and sub-tasks in sync
Keep the status of parents and sub-tasks in sync
Manually create test issues
Manually delete test issues
Notify about date of last comment for high priority issues
Notify assignees when components are merged
Notify for high priority issue
Notify the assignee one week before the due date
Notify the project lead on priority changes

If you still have questions, feel free to refer to our support team.

Content

Space Tools

On this page

Use case