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).*
stylecircle
typeflat
separatorpipe

Create a sub-task for each selected component in

your project

the current issue, you can make use of this function to avoid repetitive tasks when you have multiple components and want to create a sub-task for each.

 

UI Text Box
sizemedium
typeinfo

Use case

Panel
borderColor#1b878f
titleColor#1b878f
titleBGColorwhite
titleUse case details
Page properties
Function

<link to function being used>

Type

Image RemovedPost function

Use case description
Complexity

Status
colourGreen
titleBeginner

Image RemovedConfiguration steps

Basic configuration*

Image Removed

UI Expand
titleMode*

When you apply the example from the create issue post function in your Jira instance, it will create a single issue.

Code Block

Image AddedConfiguration

UI Steps
UI Step

Add a Create issue post function to the workflow transition you want.

UI Step

Issues to be created

UI Steps
UI Step

Mode

Choose Multiple issues.

UI Step

Expression

Code Block
linenumberstrue
titleExpression*
toStringList(%{issue.
component}) The expression must return a string list. The number of list elements defines the number of issues to be
components})

with parsing mode set to Text list.

UI Text Box
iconfalse
typeinfo

The number of list elements defines the number of issues to be created.

ui-
expand
step
title

Issue type

*The issue type is the selected

Choose Selected issue type.

i.e the issue type that is currently selected.

ui-
expand
step
title

Specific issue type

In the example given on the left, we chose the "sub-task" issue type, so it will create a sub-task for the selected issue type

Choose Sub-task.

ui-
expand
step
title

Parent issue

*Here we have chosen the "Current issue" for the required field parent

Choose Current issue.

ui-
text-box
step
typeinfo
Choosing another specific issue type, e.g task or epic, will have an effect on the Parent issue parameter, it will be visible as Project and not Parent issue.

Summary

Enter the following expression 

Fields*

Code Block
title
language
Summary
Summarize your issue , and you can also use field codes 
Code Block
titleDescription
Describe your issue, and you can also use field codes

Additional fields

UI Expand
titlecopy remaining fields

Choose from which issue you want to copy the remaining fields from.

If you chose an issue to copy from you would have to choose between the following options (multi choice is possible):

  •  All remaining fields
  •  Attachments
  •  Comments
  •  Issue links
bash
linenumberstrue
"Sub-task related to " + %{seed.text}

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.


Image AddedScreenshots

Image Added


Image Added

After checking if the parameters match this example you can click on add and see how the post function works.

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

Related examples

Page properties report
firstcolumnUse case
headingsTypeJWT feature, Function, Use case description, ComplexityWorkflow function, Parser functions, Label
sortByTitle
cqllabel = "use-case-workflow" and space = currentSpace() and parent = currentContent()
If you still have questions regarding this example or others, feel free to refer to our support team.
ancestor = "27066752"


Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue

Page properties
hiddentrue
JWT feature

Image Added

Workflow function

Create issue

Parser functionstoStringList()
Label
Page properties
hiddentrue

Status
Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

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