issueFieldExactMatch

The issueFieldExactMatch function provides an exact text match within specified fields of issues selected by a subquery. This is particularly useful for:

Ensuring precise data retrieval when the exact text is known and variations or partial matches are not acceptable.
Enabling strict compliance checks, where exact wording or data entry must be verified against predefined standards.
Streamlining searches that require absolute accuracy, such as matching exact error messages, specific labels, or unique identifiers.

Syntax and parameters:

issueFieldExactMatch(Subquery, FieldName, Pattern Match)

Subquery: A JQL query that narrows down the set of issues to be searched. It's important to limit this to a manageable subset to optimize performance.
Field name: The name of the field in which to search for an exact match. This can be any standard or custom field within Jira.
Pattern match: The text pattern that must be matched exactly within the specified field.
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.

Examples

Finding issues with exactly matched error codes:
To locate issues where a custom field exactly matches a specific error code:
1
```
issueFunction in issueFieldExactMatch("project = ERRORS", "customfield_10022", "^ERROR-0123$")
```
This query ensures that only issues with the custom field customfield_10022 containing precisely "ERROR-0123" are retrieved, crucial for tracking specific errors or issues.
Ensuring compliance with documentation standards:
For verifying that certain documentation standards are exactly met within issue descriptions:
1
```
issueFunction in issueFieldExactMatch("project = DOCS", "description", "^Documented as per standard$")
```
This can be used in scenarios where precise language use is critical, such as legal clauses or regulatory compliance statements in issue tracking.

Tip:

Precise Pattern Match: Ensure they are designed to match the entire field content from start to end using anchors ( ^ and $) to avoid partial matches.

Optimise Performance Through Subquery: Since performance is dependent on the number of issues processed, refine your subquery to be as specific as possible, reducing the workload on the system.

Regular Audits and Checks: Utilise this function for regular audits and checks to ensure ongoing compliance with operational or regulatory standards.