Disclosure: Snapbytes is the developer of SnapJQL.
Sometimes you do not need the whole hierarchy—only a property from the parent
A common Jira question sounds simple: “Show me child issues whose parent is in progress,” or “Find subtasks under high-priority stories.” The child issue itself does not contain that parent value in a way that standard JQL always makes convenient.
The result is often a two-step workflow: search the parents, copy keys, then build another query for the children.
Parent and child properties make cross-level filtering direct
SnapJQL exposes indexed properties such as parent key, parent summary, parent issue type, parent priority, parent status, and parent status category. These properties can be used directly in JQL expressions with familiar operators.
That means the query can describe the relationship in the same place as the child criteria instead of maintaining a separate list of parent keys.
Example: find work blocked by parent state
Suppose a delivery team wants all subtasks whose parent story is still In Progress, but only for one project and only where the subtask itself is not Done. A cross-level property lets the search express the parent condition without a manual parent lookup.
This is useful for quality checks, handoff reviews, release preparation, or boards where the state of the parent changes how the child work should be interpreted.
Use relationship properties when traversal is unnecessary
Recursive hierarchy functions are powerful, but they are not always the simplest tool. If the question is specifically about one level—child issues filtered by parent attributes, or vice versa—a direct property can be easier to read and maintain.
Choose the smallest query that explains the business question clearly.
If you keep maintaining lists of parent keys just to filter their children, explore SnapJQL on Atlassian Marketplace and try the indexed parent and child properties directly in Jira search.
