JQL Search

Starting with version 1.0.1, the Jira Issue Picker field can be used as a search criterion directly in JQL.

This functionality allows you to build advanced queries to find issues based on the value contained in your Issue Picker fields. The search is always performed by comparing the Issue Key of the issue stored in the field.

Supported Operators

Below is a table with the operators you can use and practical examples. For the examples, we will assume you have a custom field named "My Issue Picker".

Operator	Example Usage	Description
!=	"My Issue Picker" != "PROJ-123"	Finds all issues where the "My Issue Picker" field does not contain the issue PROJ-123.
IN	"My Issue Picker" in ("PROJ-123", "PROJ-456")	Finds issues where "My Issue Picker" contains any of the issues specified in the list.
IS EMPTY	"My Issue Picker" IS EMPTY	Finds all issues where no value has been selected in the "My Issue Picker" field.
IS NOT EMPTY	"My Issue Picker" IS NOT EMPTY	Finds all issues that have a value selected in the "My Issue Picker" field.

Use Case: Filtering Issues by Dependencies

To illustrate how to use the operators, let's imagine a real scenario in the Phoenix Project (PHX). You have an Issue Picker field named "Issue bloqueante" that you use to mark dependencies between tasks.

Finding issues with no blockers (IS EMPTY)

You want to find all issues in the project that are not blocked by any other issue. To do this, you can use the IS EMPTY operator.

JQL Example:

"Issue bloqueante" IS EMPTY

Expected Result: This query will return all issues where the "Issue bloqueante" field is empty.

---

Finding issues blocked by specific tasks (IN)

Now, you want to see which issues are specifically blocked by tasks PHX-1 or PHX-2. The IN operator is perfect for this.

JQL Example:

"Issue bloqueante" IN (PHX-1, PHX-2)

Expected Result: This query will return issues PHX-3 and PHX-4, which are the ones that have PHX-1 and PHX-2 in their "Issue bloqueante" field, respectively.