versionMatch
The versionMatch function allows you to search for issues where version fields contain specific text patterns you define.
This function is highly beneficial for:
- Streamlining the management of releases by enabling teams to quickly identify all issues associated with specific versions or version patterns.
- Enhancing the accuracy of queries about version-related tasks, particularly useful in large projects where numerous versions are released over time.
- Facilitating targeted actions or reports related to certain release cycles, especially when preparing for a version rollout or audit.
How to use the versionMatch JQL function demo video
Syntax and parameters:
versionMatch(Pattern Match, [Project Keys])Pattern match: the specific pattern of text you are looking for in version fields. This helps you to find versions that start with certain letters or numbers, contain specific characters, or meet other criteria you define.
- Syntax: Our example below uses regex syntax. You can refer to this website, which is a regular expression builder that can help you build an expression and provides definitions for each of the characters.
Project keys (optional): A comma-separated list of project keys to narrow down the search. Specifying project keys improves query performance by limiting the search scope.
Examples
Finding issues with versions starting with RC across all projects:
For teams needing to track release candidate versions:
fixVersion in versionMatch("^RC.*")This query helps in quickly identifying all issues that are part of any release candidate versions across all projects, useful for status reviews or release preparations.
Restricting the search to specific projects:
To enhance performance and focus on specific projects:
fixVersion in versionMatch("^RC.*", "DEMO, EXAMPLE, TEST")By specifying projects, the function narrows down the search, making it more efficient and tailored to particular project needs.
- Use a specific pattern match: Allows you to accurately capture the versions of interest without being overly broad, which could impact performance.
- Regularly update project keys: Keep the list of project keys up-to-date in your queries to reflect any changes in project configurations or priorities.
- Monitor query performance: Be aware that using
versionMatchacross a large number of versions or projects without specifying project keys can lead to slow performance. Always try to use project keys where practical.