Versions Compared

Key

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


Panel

On this page

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

Page properties
hiddentrue



<link to function being used>
UI Text Box
sizemedium
typeinfo
Function

Use case

description
When an issue is created, 3 sub-tasks, Documentations, Marketplace and Newsletter are added to this issue.
Complexity

Status
colourGreen
titleBeginner

Info
titleUse case

When an issue is created, 3 sub-tasks, Documentations, Marketplace and Newsletter are added to this issue.

Image RemovedConfiguration steps

Follow these steps to create the add sub-task rule.

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?


UI Text Box
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.





steps
UI Steps

Image ModifiedIssue Created event

ui-
stepProviding a description will help you to identify what the rule does but this step is optional.
stepui
Excerpt-
Include Page
DECADIS:Automation Use Case - Create Rule Step
DECADIS:Automation Use Case - Create Rule Step
nopaneltrue

Create a new rule and name it appropriately.

UI Text Box
typeinfo


UI Step
Choose trigger:

Add a Trigger → Issue Event  Issue Created


Image Added 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"
Choose the event: Issue Created event


UI Text Box
typeinfo

No further configuration needed. The automation rule is triggered every time an issue is being created.

Image RemovedCreate Issue
Replace key1, key2 and key3 with your project keys.



Image Added 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

Type number 3 and change the with parsing mode set to Date/Mathematical


UI Step

Issue type

*

Choose Choose Sub-task


UI Step

Parent issue

*

Choose Trigger issue




UI Tab
titleFields


UI Steps


UI Step

Summary

*

Use the following parser expression Parser Expression:

laksndlkandsads

adsadsads

ads
Code Block
linenumberstrue
getMatchingValue(^,[1,2,3],
["Documentation","Marketplace","Newsletter"])
Expand
titlemore info...

with parsing mode set to Advanced text.


UI Step

Description

*

Use the following parser expression 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 text.






UI Step

Click on add, and then activate the rule by clicking on the activate rule button Image Removed

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




Image AddedScreencast

This is how the configuration above should look on your screen

Multimedia
nameadd_sub-tasks_to_issue_on_creation.mp4
width700


Image AddedImport the example

Import the JSON file below to get started in no time.


UI Expand
titleJSON


UI Text Box
typewarning

After importing the JSON file, make sure to check the configuration of the rule. Non-existing configuration elements (issue types, fields, values etc.) will be highlighted.


Code Block
languagejs
themeMidnight
linenumberstrue
{
    "name": "Add sub-tasks to issue on creation",
    "description": "",
    "creator": "admin",
    "status": false,
    "triggerData": "1",
    "triggerType": "ISSUE_EVENT",
    "configuration": {
        "refs": [
            "issue",
            "system",
            "trigger.issue",
            "trigger.parent"
        ],
        "triggerType": "1"
    },
    "children": [
        {
            "sequence": 0,
            "type": "CREATE_ISSUE",
            "ruleEntityType": "ACTION",
            "configuration": {
                "refs": [
                    "issue",
                    "project",
                    "system",
                    "trigger",
                    "trigger.issue",
                    "trigger.parent",
                    "remote.math"
                ],
                "issueSelectionParserValue": "3",
                "issueSelectionParserValueParsingMode": "math",
                "issuetype": "5",
                "parentSelection": "eventIssue",
                "parentIssueKeyParsingMode": "textBasic",
                "projectKeyParsingMode": "textBasic",
                "actingUser": "field_00020",
                "summary": "getMatchingValue(^,[1,2,3],\r\n[\"Documentation\",\"Marketplace\",\"Newsletter\"])",
                "summaryParsingMode": "textAdvanced",
                "description": "getMatchingValue(^,[1,2,3],\r\n[\"Issue for creating the documentation for the feature\",\r\n\"Issue for updating the marketplace presence for the app\",\r\n\"Issue for creating a newsletter for the feature\"])",
                "descriptionParsingMode": "textAdvanced",
                "inheritFieldsFrom": "none",
                "inheritFieldsIssueKeyParsingMode": "textBasic",
                "inheritIssueLinks": "none",
                "inheritIssueLinksIssueKeyParsingMode": "textBasic",
                "fields": [
                    {
                        "field": {
                            "label": "Assignee",
                            "value": "00003",
                            "meta": {
                                "isStringEphemeral": false,
                                "isCustomField": false,
                                "isIndexable": false,
                                "isCalculated": false,
                                "isMultiValued": false,
                                "type": "User",
                                "isNumericEphemeral": false,
                                "isSystemField": true,
                                "hasStandardConfig": true,
                                "isSubtaskOnlyField": false,
                                "isMultiWritable": false,
                                "isNumericField": false,
                                "isVirtualField": true,
                                "id": "3",
                                "key": "assignee",
                                "isClearable": true
                            }
                        },
                        "valueType": {
                            "label": "Value returned by parsed expression",
                            "value": "parser"
                        },
                        "value": {
                            "label": "% Creator (Trigger)",
                            "value": "%{trigger.issue.creator}"
                        },
                        "parsingMode": {
                            "label": "Advanced",
                            "value": "textAdvanced"
                        }
                    }
                ],
                "issueLinks": [],
                "issueSelection": "math",
                "inheritFields": []
            },
            "children": null,
            "hasChildren": false
        }
    ],
    "hasChildren": true
}




Image AddedRelated use cases

Page properties report
headingsAutomated action, JWT feature, Label

After checking if the parameters match this example, you can click on add and this is how the rule should look like.

Now that you are familiar with this rule and what it does, you can configure the parameters based on your needs.

Image RemovedRelated examples

The following list has examples that you might find useful

Page properties report
firstcolumnUse case
headingsType,Function, Use case description, Complexity
sortByTitle
cqllabel = "use-case-auto" and label = "create-issue" and space = "JWTSDC"
If you still have questions regarding this example or others, feel free to refer to our support team.


Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Page properties
hiddentrue


JWT feature

Image Added

Automated actionCreate issue action
Label




Page properties
hiddentrue



Status
Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Status
titleto do
Status
colourGreen
titledone
Status
colourYellow
titleneeds review
Status
colourRed
titleflagged