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)
