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}
^%{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.
Examples:
- 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)
These values specify the number of actions to be performed or the
The number of actions the are retrieved from an issue list (e.g. subtasks() or [JWT-1, JWT2]
Each issue will be individually selected and processed. During that process these individual issues are called seed issues.
In functions and examples using this feature you will notice the ^ symbol in front of a field code. This means that JWT will take the value from exactly the issue that is currently being processed.
Example:
You want to create a subtask for each issue returned by a JQL query. Each issue returned by the query is a seed issue. Values in each issue can be referenced by ^<fieldCode>
