JQL Syntax
It is possible to use a simple syntax in Jira using the custom field "Requirement Yogi info". Please note that this custom field only contains text, and has a character limitation. You can use the Beta JQL Extensions for more accurate results.
Example:
JQL Extension
| Note |
|---|
This function is still in beta, as the underlying Atlassian API is still in preview. |
...
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.
...
Syntax
You can use the issue in hasReq() or issue in hasRequirement() syntax. Both functions are aliases of each other.
...
Search parameters
Argument | Description | Example |
|---|---|---|
Project name | [Optional, default = ““] → Restrict the issues to a specific project |
|
Search offset | [Optional, default = 0] → Pagination parameter. Useful when your query matches too many issues |
|
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 |
|
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. |
Find the first 100 issues containing requirement in all projects and force Atlassian to use the most up to date results |
...