The JQL parsing mode, just like the Issue list mode, lets you define a target selection of issues. It is being used in Post functions and Automation actions, that allow you to create or updated multiple issues. Therefore it is being used in:

• Create issue workflow post function
• Update fields workflow post function
• Transition issue workflow function
• Log work workflow post function
• Read fields from linked issues or sub-tasks workflow post function
• Create issue action - Automation
• Update field action - Automation
• Transition issue action - Automation
• Log work action - Automation

The output has to be a valid issue list as defined in the Data types section. The input must be a valid JQL query where you can also use field codes.

Additionally JWT expression parser functions can be used.

• If field values are expected to have white spaces or JQL reserved words or characters, you should enclosed the field code in quotes (double or simple). Example: summary ~ "%{00021}" will return issues with the current user's full name in the summary. As full name can contain spaces, the field code was enclosed in double quotes.
• Anyway, there is an exception to this general rule: when our field contains a comma separated list of values, and we want to use it with the JQL operator IN. In those cases we will not write the field code between quotes, since we want the content of the field to be processed as a list of values, not as a single string value.

Make sure to read all about working with Lists as they come with many extremely useful JWT expression parser functions.

List functions can also be used in the Advanced text mode. The difference is, that the output will be a flat text instead of an issue list.

The main advantage over the advanced text mode is, that you can use the returned elements of the issue list as Seeds.