JWT is capable of processing values from multiple sources (e.g. issues, custom fields etc.). These sources are called seeds.
The following seeds are available:
- Seed issues: All issues that are found or returned by an issue list
- Seed strings: Strings, or texts, that are usually returned by a text list (e.g. custom field option list, list of components etc.)
- Seed numbers: Fixed numbers or numbers returned by a calculation
If values from a seed source are needed to perform actions, the field codes need to be precedented with ^ or the word seed.
%{seed.issue.summary} # is the same as
^%{issue.summary} |
JWT iterates over each seed and performs an action based on the values being found or specified. Whatever function or action you specify will be performed for each seed JWT recognizes.
Hier wäre doch ein Screencast wunderbar 
"Seeds in 60 seconds" - Oder erklärende Grafiken
Examples: to be linked and created
Create three subtasks and use each of the three current components as a summary - each component is a seed string
Create a task for each Epic returned by a JQL query - each epic is a seed issue
Add 4 comments - 4 is a seed number (since JWT will perform the action 4 times)
Probably most of the time, doing things with the help of JWT is related to a single object - the issue currently being transitioned, e.g. by adding a comment, updating a field, sending an email, etc.
Referring to the current issue's information can be done by using a simple Field code like %{issue.description}.
However, since you can also use more complex functions in JWT that work with multiple objects, this simple notation is not sufficient for those use cases. To name a few examples
- Creating sub-tasks based on the (dynamic) selection of components set in the current issue
- Create a task for each issue returned by a JQL query (dynamic)
- Create a set of three (static) stories in an Epic with distinct pieces of information
Whenever Jira Workflow Toolbox has to handle (or iterates over) multiple elements of a list (or sources), those elements are referred to as seeds. Depending on the type of list, those are referred to as
- Seed issues - for issue lists
- Seed texts - for text lists (e.g. custom field option list, list of components etc.)
- Seed numbers - for number lists
Seed issues
Issue lists can be specified by JQL queries, issue list expressions, or (in some post functions or automation actions) the selection of explicit options, e.g. Issues under Epic.
When dealing with issue lists, the notation for accessing values of each element is %{seed.issue.someField}, e.g. %{seed.issue.summary}
Workflow functions and automation actions
You might face seed issues when trying to create/update/transition multiple issues.
- Multiple issues → JQL
An issue is created for every issue returned by the JQL query. - Multiple issues → Issue list
An issue is created for every issue returned by the issue list expression.
Given 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, the post function will run three times, where the following values will be returned throughout those three runs
| Run | %{seed.issue.key} | %{seed.issue.summary} |
|---|
| 1 | DEMO-1 | Issue A |
| 2 | DEMO-2 | Issue B |
| 3 | DEMO-3 | Issue C |
In general, using the seed notation, the nth run returns the field values of the nth issue from this list.
This works exactly the same when choosing the Issue list mode, e.g. given the expression parser function linkedIssues() returns the same issues like shown before, the result
Further workflow functions and automation actions using seed issues
Expression parser functions
List functions like mathOnIssueList() or textOnIssueList().
tbd.
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.%{issue.cf123456}}) (where the custom field with the ID 123456 is a multi option custom field).
When dealing with text lists, the notation for each element %{seed.text}.
Workflow functions and automation actions
- Multiple issues → Text list
An issue is created for each element of a text list.
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
| Run | %{seed.text} |
|---|
| 1 | firstElement |
| 2 | secondElement |
| 3 | thirdElement |
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
| Run | %{seed.text} |
|---|
| 1 | Frontend |
| 2 | Backend |
After adding a third component Interface, the post function will run three times returning the following values for each run
| Run | %{seed.text} |
|---|
| 1 | Frontend |
| 2 | Backend |
| 3 | Interface |
That said, composing a summary with an expression like
"Summary of " + %{seed.text} + " Issue"
would result in three issues, named
- Summary of Frontend Issue
- Summary of Backend Issue
- Summary of Interface Issue
Further workflow functions and automation actions using seed texts
Expression parser functions
List functions like mathOnStringList() or textOnStringList()
tbd.
Seed numbers
Number lists can either be static, e.g. [1, 2, 3], or composed dynamically by using the toNumberList() expression parser function.
Single numbers can either be static, e.g. 3, or calculated by using expression parser functions.
When dealing with number lists, the notation for each element is %{seed.number}.
Workflow functions and automation actions
- Multiple issues → Numeric mode
The number of issues provided by the numeric value is created.
Given a static example with the numeric value being 3 in order to create three issues, the following values will be returned for each run
That said, composing a summary with an expression like
"Summary of Issue #" + %{seed.number}
would result in three issues, named
- Summary of Issue #1
- Summary of Issue #2
- Summary of Issue #3
Further workflow functions and automation actions using seed numbers
tbd.
Expression parser functions
List functions like mathOnNumberList() or textOnNumberList()
tbd.