Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

Versions Compared

Old Version 7

changes.mady.by.user Iheb Kharab

Saved on

compared with

New Version Current

changes.mady.by.user Vicente Domínguez Navarro

Saved on

Key

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


Panel

On this page

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



UI Text Box
sizemedium
typeinfo

Use case

Creating repetitive issues might be time-consuming work, especially when done on a daily basis. This post function can be used for pre-configuring a set sub-tasks.

Each time the transition is executed, all needed sub-tasks will be created depending on the selected values in a checkbox field.


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


UI Text Box
typetip

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

This use case is very useful, if repetitive issues have to be created in only one project or workflow. Then a post function is the easier way to go.

But if this setup is needed for several projects, the Create issue action would make more sense.  In this case you might want to check out our corresponding automation use case.



Image ModifiedConfiguration

UI Steps


UI Step

Add an a Create issue post function to the desired workflow transition.

UI Text Box
typetip

The Create issue transition might be here the best choice, though. When added to the Create issue transition, the post function will be automatically executed each time an issue is created.



UI Step

Issues to be created

UI Steps


UI Step

Mode

*

Choose Multiple issues


UI Step

Expression

*

Enter the following parser expression

Code Block
languagebash
linenumberstrue
toStringList(%{issue.cfnnnnn})
# Replace the field code with the fieldone code of your custom field. Use the field dropdown to automatically insert the field code.
# You can mightuse wantany tofield usesupporting amultiple checkbox or select custom fieldoptions, e.g. checkboxes or multi-selects.

with parsing mode set to String ListText list


UI Step

Issue type

*

Choose Selected issue type → Sub-task


UI Step

Parent issue

*

Choose Current issue




UI Step

Summary

*

Enter the following expression

Code Block
languagebash
linenumberstrue
^%%{seed.text}
# This is a reference to each value returned by the stringtext list.

with parsing mode set to Advanced Text


UI Step

Description

To enrich the issue with further information, you might want to add a short description. It is not mandatory, though.


UI Step

Run as

User

*

Choose Current user




Image ModifiedScreenshots

Image RemovedScreencast

Image Added


Image ModifiedRelated use cases

Page properties report
firstcolumnUse case
headingsJWT feature, Workflow function, Parser functions, Label
sortByTitle
cqllabel = "use-case-workflow" and ancestor = "27066752"

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Page properties
hiddentrue


Create sub-tasks depending on selected values in a custom field (like checkboxesComplexityGreen   
JWT feature

Workflow function

Create issue

Use case description
Parser functionstoStringList()
Label

Status
colour

Red
title

Beginner

staff pick



Page properties
hiddentrue



Status
Tech review

Status
colourGreen
titletododone

Style guide

Status
colourGreen
titletododone

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