Page History

Image AddedSeed issues

Issue lists can be specified by JQL queries, issue list expressions, or (in some post functions or automation actions)

by predefined selections, e.g. Issues under Epic.

Workflow

functions and automation actions

You might face seed issues when trying to

create/update/transition multiple issues.

• Create issue post function

• Create issue action

Example: You want to create multiple issue based on a a custom JQL that returns three issues:

• DEMO-1 Issue A
• DEMO-2 Issue B
• DEMO-3 Issue C

Creating issues based on this JQL query, the post function will run three times, where the following values will be returned throughout those three runs

In general, using the seed notation, the nth run returns the field values of the nth issue from this list.

When choosing the Issue list mode, e.g.

with an expression like linkedIssues()

, the behavior is the same

.

Further workflow functions and automation actions using seed issues

• Transition issues post function

• Update or copy field values post function
• Condition on a list of issue keys or Validation on a list of issue keys
• Condition on linked issues or Validation of linked issues
• Condition on sub-tasks or Validation of sub-tasks

Image Added

Seed texts

Text lists can either be

• static, e.g. ["firstElement", "secondElement", "thirdElement"], or
• composed dynamically

•  by using the toStringList() expression parser functions, e.g. toStringList(%{issue.components}) or toStringList(%{issue.

• cf12345}}) (where the custom field with the ID 123456 is a multi option custom field) or
• calculated by using one of the functions that return a text list like fieldHistory(), groupsUserBelongsTo() etc., e.g. fieldHistory(%{issue.summary}}) or groupsUserBelongsTo(%{system.currentUser}})

Workflow functions and automation actions

Create issue post function

Number of issues to be created	Mode	Description
Multiple issues

Given the example of a static list above, the post function will run three times and the following values will be returned throughout those three runs

Given a dynamic example, having selected the components Frontend and Backend on an issue, the post function will run two times returning the following values for each run

After adding a third component Interface, the post function will run three times returning the following values for each run

According to this scenario, composing a summary with an expression like

"Summary of " + %{seed.text} + " Issue"

will result in three issues, named

• Summary of Frontend Issue
• Summary of Backend Issue
• Summary of Interface Issue

Expression parser functions

List functions like mathOnStringList() or textOnStringList()

Examples

• Create a sub-task for each component

Image AddedSeed numbers

Number lists can either be

• static, e.g. [1, 2, 3], or
• composed dynamically by using the toNumberList() expression parser function

• or
• calculated by using one of the functions that return a number list like releaseDates(), timesOfTransition(), etc.

• , e.g

• . releaseDates(%{issue.fixVersions}) or timesOfTransition("Done","Open"})

Workflow functions and automation actions

• Create issue post function or 
• Create issue action

Given a static example with the numeric value

of 3 in order to create three issues, the following values will be returned for each run

The number 3 is interpreted as a number list [1, 2, 3

].

According to this scenario, composing a summary with an expression like

"Summary of Issue # " + {seed.number}

will result in three issues, named

• Summary of Issue

• # 1
• Summary of Issue

• # 2
• Summary of Issue

• # 3

Expression parser functions

List functions like mathOnNumberList() or textOnNumberList()