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 99

changes.mady.by.user Ute Masermann

Saved on

compared with

New Version 100

changes.mady.by.user Iheb Kharab

Saved on

Key

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


UI Text Box
sizemedium
typeinfo

This post function automatically creates one or multiple standard issues or sub-tasks in any given project.

The issue(s) that will be created can be entirely customized - from dynamically determining the issue type to presetting or inheriting field values.


Configuration

UI Expand
titleMode

The mode parameter defines how many issues you want to create. The following modes are available:

OptionDescription
Single issue

If you select this mode, you will be dynamically guided to ultimately specify what issue type will be created and where it will be created. This may include a multi-layered selection process.

You can either pick the issue type from a list of available issue types or manually define the type using a parser expression.

Depending on each selection, additional parameters will be shown. These parameters depend on the context or your previous selection - for example:

  • a parent issue needs to be chosen, when a sub-task is being created
  • a project needs to be selected, in which the issue will be created

In this mode, only one single issue will be created.

Multiple issues
If you want multiple issues to be created at once, you will be given various options to specify
  • how many issues will be created
  • which issue types they will have and
  • where they will be created 

Determining the number of issues is done using a parser expression. The output will depend on the selected parsing mode. The following options are available:

  • Number: The expression must return a number that defines the number of issues to be created. The most obvious way to achieve this is by simply adding a number.
  • JQL: The number of issues returned by the JQL query defines the number of issues to be created.
  • Issue list: The number of list elements defines the number of issues to be created.
  • Text list: The number of list elements defines the number of issues to be created.

Include Page
DECADIS:_snip_tryExpression
DECADIS:_snip_tryExpression



UI Expand
titleIssue type

Select the issue type of issue(s) to be created. The following options are available:

OptionDescription

Selected issue type

Select the issue type for the issue to be created. Depending on the selection additional parameter will be available.

In case you choose a standard issue type, the project you want to create the issue in has to be defined. The following options are available:

  • Current project
  • Selected project
  • Seed issue's project (only available if multiple issues were selected and JQL mode or Issue list mode was used to set the value)
  • Set project manually (parser expression)
UI Text Box
typenote

If you want to dynamically set the project using an expression, make sure it returns a project name or project key.


In case you choose a sub-task, the respective parent has to be selected and the following options are available:

  • Current issue
  • Parent of current issue
  • Seed issue (only available if multiple issues were selected and JQL mode or Issue list mode was used to set the value)
  • Set parent manually (Parser expression)
UI Text Box
typenote

If you want to dynamically set the parent using an expression, make sure it returns a single issue key.

Especially when using the JQL mode or Issue list mode, that return a list of multiple issues.


Parser expression (standard issue type)

If you want to dynamically set the issue type using an expression, make sure it returns an issue type name.

Parser expression (sub-task issue type) If you want to dynamically set the sub-task issue type using an expression, make sure it returns a sub-task issue type name.



UI Expand
titleFields

Summary

Define the summary of the issue(s) to be created.

Include Page
DECADIS:_snip_generic_expression_editor
DECADIS:_snip_generic_expression_editor

Description

Define the description of the issue(s) to be created.

Include Page
DECADIS:_snip_generic_expression_editor
DECADIS:_snip_generic_expression_editor

Additional fields

You can optionally set additional field values. After clicking the Add button you can define how to set the values.

Include Page
DECADIS:_snip_available_options
DECADIS:_snip_available_options

OptionDescription
AutomaticThis option is only available for the field Assignee.
Selected valueSelect a specific value from the dropdown list.
Copy field value from current issueCopy the value from a field in the current issue. Select the field you want to copy the value from.
Copy field value from epic issueCopy the value from the related Epic issue. Select the field you want to copy the value from.
Copy field value from seed issue

Copy the value from a seed issue. This option is only available if multiple issues were selected and JQL mode or Issue list mode was used to set the value).

Copy field value from parent of new issueThis option is only available if you create a sub-task under a new parent. Only available if the issue to be created is a sub-task.
Set field value manually (parser expression)

Select the field to copy from using an expression. 

Include Page
DECADIS:_snip_generic_expression_editor
DECADIS:_snip_generic_expression_editor

Copy remaining fields

Set this parameter if you want to optionally copy or clone all (remaining) field values from an issue. 

Include Page
DECADIS:_snip_available_options
DECADIS:_snip_available_options

OptionDescription
Don't copy fieldsBy default no other field values will be copied.
From current issueAll other field values will be copied from the current issue.
From parent of current issueAll other field values will be copied from the parent of the current issue.
From parent of new issueAll other field values will be copied from the parent of the sub-task to be created. Only available if the issue to be created is a sub-task.
From seed issue

All other field values will be copied from a seed issue. This option is only available if multiple issues were selected and JQL mode or Issue list mode was used to set the value).

From epic issueAll other field values will be copied from the related Epic issue.



UI Expand
titleIssue links

Issues to be linked

Optionally define issue links to be created for the new issue(s). You have the option to link the issue that you are currently creating to various other issues. 

Include Page
DECADIS:_snip_available_options
DECADIS:_snip_available_options

OptionDescription
Current issueLink the issue(s) to be created to the current issue.
Parent of current issueLink the issue(s) to be created to the parent of the current issue.
Parent of new issueLink the issue(s) to be created to the parent of the sub-task to be created. Only available if the issue to be created is a sub-task.
Epic of current issueLink the issue(s) to be created to the related Epic of the current issue.
Seed issue

Link the issue(s) to be created to a seed issue. This option is only available if multiple issues were selected and JQL mode or Issue list mode was used to set the value)

Select issues manually (parser expression)

Include Page
DECADIS:_snip_issue_selection_expression_editor
DECADIS:_snip_issue_selection_expression_editor

Condition

You can optionally define a condition which must be met for the link to be created. The expression can be set using the Logical mode.


UI Expand
titleAdditional options

The only available additional option is Store issue keys.

If this option is checked, all issue keys from the issue(s) to be created will be stored in the field temporary text 3 as a comma separated list. 


UI Expand
iconfalse
titleConditional execution

Include Page
DECADIS:_snip_condExecution_Server
DECADIS:_snip_condExecution_Server


UI Expand
iconfalse
titleRun as

Include Page
DECADIS:_snip_runAs_Server_postFunction
DECADIS:_snip_runAs_Server_postFunction



Use cases and examples

Page properties report
firstcolumnUse case
headingsJWT feature, Workflow function, Parser functions, Label
cqllabel = "use-case-workflow" and parent = currentContent()

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


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


Page properties
hiddentrue


Short descriptionCreate one or multiple issues or sub-tasks.
Label

Status
colourRed
titlestaff pick