On this page
Use case
Often creating repetitive issues is daily work, e.g. in a software development release process. It might be that for each 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.
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. Therefore, you can also check out our corresponding post function 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 and choose Issue Event → Issue Created
No further configuration needed. The automation rule is triggered every time an issue is being created.
Create Issue action
Issues to be created*
Choose Multiple issues
Parser Expression*
3
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"])
Click on add, and then activate the rule by clicking on the activate rule button →
Screencast
This is how the configuration above should look on your screen
Related examples
If you still have questions regarding this example or others, feel free to refer to our support team.
