JQL use cases

This is the documentation for JSU for Jira Cloud. If you are using JSU on Jira Server or on Jira Data Center, see the Server/Data Center documentation.

We built integrated JQL in many of our workflow post functions, allowing Jira administrators to set wider parameters that can be fully customized.

On this page: 1 JQL in post functions 1.1 Use Case 1: Update the Description of particular sibling issues 1.2 Use case 2: Copy fields from a template issue 1.3 Use Case 3: Change the status of critical issues in an Epic

On this page: 1 JQL in post functions 1.1 Use Case 1: Update the Description of particular sibling issues 1.2 Use case 2: Copy fields from a template issue 1.3 Use Case 3: Change the status of critical issues in an Epic

Below, you will find a few examples demonstrating how flexible and powerful JQL can be when used with JSU. Refer to the JQL Reference for details on how to use JQL with JSU.

JQL in post functions

In several JSU post functions, you can specify a JQL query to retrieve the issues to be modified by the post function. See also Related Issues.

Use Case 1: Update the Description of particular sibling issues

Post function: Update Any Issue Field
Transition: Resolve in our Testing Subtask workflow

Screenshot of the Update Any Issue Field configuration as described on this page.

Use case 2: Copy fields from a template issue

Post function: Copy Value from Other Field

We are using issue XY-23 as a template. Only Jira admins can view this issue. It has pre-configured values for several fields.

Screenshot of an example JQL query for issue key.

Use Case 3: Change the status of critical issues in an Epic

Post function: Linked Transition

If an epic has critical and blocker issues that are still in the open state, change it to in progress.