Versions Compared

Old Version 4

changes.mady.by.user Iheb Kharab

Saved on

compared with

New Version Current

changes.mady.by.user Thorsten Letschert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page properties
hiddentrue


Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Status
titletodo
Status
colourYellow
titleReady for review
Status
colourGreen
titledone
Status
colourRed
titleflagged



Panel

On this page

Table of Contents
exclude(On this page|Use case|When to use).*
stylecircle
typeflat
separatorpipe


Page properties
hiddentrue


Automated action

Create issue

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

Status
colourGreen
titleBeginner




UI Text Box
sizemedium
typeinfo

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.


UI Expand
titleShould I use an automation rule or a workflow post function?


Tip
sizemedium
typetip

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.




UI Steps

Issue Created event

UI Step
Excerpt Include
DECADIS:Automation Use Case - Create Rule Step
DECADIS:Automation Use Case - Create Rule Step
nopaneltrue


UI Step

Add a Trigger → Issue Event → Issue Created


 Boolean condition

UI Step

Add the Boolean condition and enter the following Parser Expression*

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


UI Text Box
typeinfo
Replace key1, key2 and key3 with  with your project keyskey.



 Create issue action

UI Step


UI Tabs


UI Tab
titleIssue Details


UI Steps


UI Step

Issues to be created*

Choose Multiple issues


UI Step

Parser Expression*

Code Block
linenumberstrue
3

with parsing mode set to Date/Mathematical


UI Step

Issue type* 

Choose Sub-task


UI Step

Parent issue*

Choose Trigger issue




UI Tab
titleFields


UI Steps


UI Step

Summary*

Use the following Parser Expression:

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

with parsing mode set to Advanced.


UI Step

Description*

Use the following Parser Expression:

Code Block
linenumberstrue
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.






UI Step
Excerpt Include
DECADIS:Automation Use Case - Enable Rule
DECADIS:Automation Use Case - Enable Rule
nopaneltrue



Screencast

This is how the configuration above should look on your screen

Multimedia
nameadd_sub-tasks_to_issue_on_creation.mp4
width700

Related use cases

Page properties report
firstcolumnUse case
headingsAutomated action, Use case description, Complexity
sortByTitle
cqllabel = "use-case-auto" and label = "create-issue" and space = "AUTOMATION"

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue

...