Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This function is still in beta, as the underlying Atlassian API is still in preview.

You can now search for issues containing requirements with JQL.

This functionality replaces the previous functionality that used custom fields to search for requirements.

We plan to extend it in the future to allow for multiple use cases in the future. If your use case is not supported at the moment, get in touch.

Search issues containing requirements

Access the JQL search from the Filters / View all issues, and click on the Switch to JQL button.

Screenshot 2024-03-18 at 11.52.23.png

Syntax

You can use the issue in hasReq() or issue in hasRequirement() syntax. Both functions are aliases of each other.

Screenshot 2024-03-18 at 11.54.59.pngScreenshot 2024-03-18 at 12.24.51.png

Search parameters

Argument

Description

Example

Project name

[Optional, default = ““]

→ Restrict the issues to a specific project

  • issue in hasReq() : Find the first 100 issues containing a requirement in all projects

  • issue in hasReq("", 0, 100) : Find the first 100 issues containing a requirement in all projects, with explicit pagination parameters

  • issue in hasReq("RYC") Find the first 100 issues containing a requirement in the project RYC.

Search offset

[Optional, default = 0]

→ Pagination parameter. Useful when your query matches too many issues

  • issue in hasReq("", 0) or issue in hasReq("", 100) or issue in hasReq("", 200) Find the first 300 issues containing requirements in all projects.

Search limit

[Optional, default = 100]

→ Pagination parameter. You should never need to use this parameter, but it is required to use the Cache Control parameter

  • issue in hasReq("", 0, 1000) Find the first 1000 issues containing requirements in all projects (Most likely will cause an error, as JQL length is limited to 1000 characters on Atlassian side)

Cache Control

[Optional, default = ““]

Atlassian automatically saves the results of calling jql functions for 7 days, depending on arguments.

Using this parameter to force a cache miss (eg: a timestamp, or a uuid) is the easiest way to get results up to date if you recently modified issue links to requirements.

  • issue in hasReq("", 0, 100, "2024-03-18T11:13:46")

  • issue in hasReq("", 0, 100, "e846db4c-6c3d-44d3-b243-ab897fafedcf")

Find the first 100 issues containing requirement in all projects and force Atlassian to use the most up to date results

  • No labels