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 1

changes.mady.by.user Jona Ittermann

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

<Use case description>

Image RemovedPrerequisites

UI Expand
titleSet up custom fields
UI Steps
UI Step

Create a multi-line text custom field

Name: Status Update

UI Step

Create a multi-line text custom field

Name: Current status

UI Step

Create a multi-line text custom field

Name: Status History

UI Step

Go to the Field configuration and set the renderer of the 3 custom fields to "Wiki Style Renderer".

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 AddedConfiguration

UI ExpandtitleSet up workflow validator

UI Steps


Message to show when validation fails

UI Step

Add a Create issue post function to the

newly created transition the Fields required or changed validator

desired workflow transition.

ui-step

Field*

Status Update

UI Step

Condition*

Is required

UI Step
Code Block
Please enter a status update!
UI Step

Once set up, the validator should look something like this:

SCREENSHOT

Image RemovedConfiguration

Status Update field

text-box
typetip

The Create issue transition might be here the best choice. 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

Target issue*

Choose Current issue

UI Step

Current Status field

UI Steps


UI Step

Mode

Choose Multiple issues

Field*

Choose Current Status


UI Step

Expression

*Set it to Advanced and use

Enter the following parser expression

Code Block
languagebash
linenumberstrue
"*" + dateTimeToString({system.currentDateTime}, "yyyy-MM-dd", USER_LANG) + "* - *" + %{system.currentUserFullName} + "*\n" + %{issue.cfnnnnn}
UI Text Box

%{issue.cfnnnnn} is the field code for the field Status Update

toStringList(%{issue.cfnnnnn})
# Replace the field code with the one of your custom field. Use the field dropdown to automatically insert the field code.
# You can use any field supporting multiple options, e.g. checkboxes or multi-selects.

with parsing mode set to Text list


UI Step

Issue type

Choose Selected issue type → Sub-task


UI Step

Parent issue

Choose Current issue




Expression*

Set it to Advanced and use the following expression

code
UI Step

Summary

Enter the following expression

Code Block
languagebash
UI Step

Status History field

UI Steps
UI Step

Field*

Choose Status History

UI Step
linenumberstrue
%{
issue
seed.
cfaaaaa
text}
+ "\n\n" + %{issue.cfbbbbb}
UI Text Box

%{issue.cfaaaaa} is the field code for the field Current Status

%{issue.cfbbbbb}is the field code for the field Status History

UI Step
UI Steps
UI Step

Field*

Choose Status Update

UI Step

Value*

Choose Clear field value

UI Step

User*

Choose Current user

UI Expand
titleAnother step
UI Steps UI Step UI Step UI Step

# This is a reference to each value returned by the text 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 AddedScreenshots

Image Added

Image RemovedScreenshots

Image RemovedScreencast


Image ModifiedRelated use cases

Page properties report
firstcolumnUse case
headingsTypeJWT feature, Function, Use case description, ComplexityWorkflow function, Parser functions, Label
sortByTitle
cqllabel = "use-case-workflow" and ancestor = "27066752"

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


 Parser hero
Page properties
hiddentrue


JWT featurelink each symbol to parent page of the function category / e.g. conditions/ validators/automation action...)>

Image Added

Workflow function

<link to function being used>

Use case description

<Short description of use case>

Label<used to mark a use case as staff pick>

Create issue

Parser functionstoStringList()
LabelComplexity
Status
colourGreen
titleBeginner
 
Status
titleIntermediate
 
Status
colourYellow
titleadvanced

Status
colourRed
title

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