Jira Snippet Library: JQL - For Software Development

Rachel Wright

Jira Software Use Cases

Here are some helpful queries, formats, and functions to use for software development.

Estimation

Jira has two built-in estimation methods. Stories often use story point estimates. Tasks often use time estimates.

Examples

• originalEstimate is not empty

• remainingEstimate > 1d

• timespent > 8h

• updated > startOfDay()

• "story points" = 2

• "story point estimate" >= 2

Note: The "Story point estimate" field is used in Team-managed spaces in Cloud.

Versions

A version is a grouping of items in a specific release.

Common Functions

• latestReleasedVersion()

• earliestUnreleasedVersion()

• releasedVersions()

• unreleasedVersions()

Examples

• fixversion = version-name

• fixversion in (version1, version2)

• fixversion is not empty

• fixversion in unreleasedVersions()

• fixversion = earliestUnreleasedVersion()

• fixversion = latestReleasedVersion()

• affectedVersion = version-name

Tip: Note that the JQL for the “Fix versions” field is singular and the “Affects versions” field uses the wording “affected version”.

Sprints

A sprint is a time-boxed iteration of rapid work.

Common Functions

• openSprints()

• closedSprints()

• futureSprints()

Examples

• Find items in created but not started sprints

  • sprint in futureSprints()

• Find items in a specific sprint

  • sprint = sprint-ID

  • sprint = sprint-name

  • sprint in (sprint1, sprint2, sprint3)

• Find items not in any sprint

  • sprint is empty

Components

A Component is a way to group similar items in a specific Jira space.

Examples

• Find items with a specific component

  • component = component-name

  • component = component-ID

  • component in (component1, component2)

---

Back to intro or article list

Bill Sheboy

Hi @Rachel Wright 

Team-managed spaces use the "Story point estimate" field, while Company-managed ones the "Story points" field.  Unfortunately, the UX is not consistent for team-managed and thus people may be further confused.  At least in JQL, the fields are consistent by their respective space types.

Aside: hopefully Atlassian will undo this design choice at some point as described in this open suggestion in JAC: https://jira.atlassian.com/browse/JRACLOUD-94950

Kind regards,
Bill