Tech review

Style guide



On this page



Automated action

Create issue

Use case descriptionAutomatically create 3 sub-tasks - Documentation, Marketplace and Newsletter.
Complexity




Use case

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.



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.





Issue Created event


Add a Trigger → Issue Event Issue Created


 Boolean condition

Add the Boolean condition and enter the following Parser Expression*

%{trigger.issue.project.key} = "key1" and %{trigger.issue.issueType} = "New Feature"


Replace key1 with your project key.



 Create issue action





Issues to be created*

Choose Multiple issues


Parser Expression*

3

with parsing mode set 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"])

with parsing mode set to Advanced.


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"])

with parsing mode set to Advanced.









Screencast

This is how the configuration above should look on your screen



Related use cases