On this page


Use case

This use case is made to create many sub-tasks with different summary and description. 

Configuration steps

Mode*

Choose Multiple issues (according to the desired number of sub-tasks).

Issue type*

Choose Selected issue type and Sub-task as its value.

Parent issue*

Select current issue.


The sub-task will be created under the current issue.

Summary*

Insert the following expression:

%{
{seed.number} = 1 ? "Summary name 1" : (
{seed.number} = 2 ? "Summary name 2" : (
{seed.number} = 3 ? "Summary name 3" : (
{seed.number} = 4 ? "Summary name 4" : (
{seed.number} = 5 ? "Summary name 5" : (
{seed.number} = 6 ? "Summary name 6" : (
{seed.number} = 7 ? "Summary name 7" : 
"Default summary"
))))))
}

Description

Insert the following expression:

%{
{seed.number} = 1 ? "Description text 1" : (
{seed.number} = 2 ? "Description text 2" : (
{seed.number} = 3 ? "Description text 3" : (
{seed.number} = 4 ? "Description text 4" : (
{seed.number} = 5 ? "Description text 5" : (
{seed.number} = 6 ? "Description text 6" : (
{seed.number} = 7 ? "Description text 7" : 
"Default text"
))))))
}

Run as*

Choose which user* will be able to execute the post function. By default, it is set to the Current user.

  Related examples

Add ancestor page for filter With ancestor

JWT feature

Workflow functionCreate issue
Parser functions
Label
Use case descriptionCopy the description of the use case here
Complexity