---
title: "Using validators"
canonical: "https://support.appfire.com/space/UTIL/18416006/Using%20validators"
format: markdown
---
> Macro (aura-html)
Additional validators and conditions enable you to perform checks in Jira based on specific criteria:
## Workflow validators
| **Workflow function** | **Description** | **Parameters** |
| --- | --- | --- |
| ### Regex Validator | Checks that input value to a custom field satisfies the Regex expression.
**Configuration: **You must specify the custom field and Regex. The custom field values will be matched by the Regex. Optionally, you can also specify a custom error message. | You can check that story points are integer.
 |
| ### Unique Field Value Validator | Checks how many different values exist for a certain field in the ticket.
**Configuration**
You must specify:
- JQL in which the result field values of issues will be compared
- Field the values for which will be compared
- Maximum allowed non-unique values of the field in a JQL result
- Alternative error message |  |
| ### JQL Validator | Checks the count of issues in a JQL result.
**Configuration**
- JQL – use %THIS% to point to a current issue key
- Number of issues which should match the JQL result count
- Alternative error message if a comment is not provided
- JQL – use %SUMMARY% to point to the current issue summary. For example: **project = "TEST" and Summary ~ "%SUMMARY%"** — checks that there is already an issue with the same summary. |  |
| ### Comment Validator | Requires a transition comment for all users except those in specified exception groups.
**Configuration**
- Specify user groups that can skip providing a comment.
- Optionally, set an alternative error message displayed when a comment is not provided. |  |
| ### Links Validator | Checks that there are no linked issues in the specified statuses.
**Configuration**
- Specify the project, issue type, and link type.
- Select the issue states to check. |  |
| ### Singular Status Validator | Checks that there are no issues in a specified status.
**Configuration**
Specify the Issue type ID and Status ID. You can find IDs at **Administration → Issues → Issue Type/Statuses** — hover over Edit and a modal appears. |  |
#### Example: Comment Validator
The following example shows how to require all users except those in the 'jira-developers' group to add a comment when transitioning a ticket.
1. Go to Jira **Administration** > **Issues > Workflows**.
2. Click **Edit** for the project where you want to add a validator.
> Macro (inline-media-image)
3. Select **Diagram** view.
> Macro (inline-media-image)
4. Select the transition where you want to add a validator. The configuration panel appears.
5. Select the **Validators** tab and click **Add validator**.
> Macro (inline-media-image)
6. Select **Comment Validator** and click **Add**.
> Macro (inline-media-image)
7. Define the validator parameters:
- (Optional) Select groups that can skip the comment when transitioning tickets.
- Specify an alternative message to prompt users to comment during a transition.
Click **Update**.
> Macro (inline-media-image)
8. To save changes, click **Publish Draft**.
9. In the dialog that appears, choose whether to back up the project copy and click **Publish**.
> Macro (inline-media-image)
10. Users who are not in the 'jira-developers' group are now required to comment every time they transition a ticket.
> Macro (inline-media-image)
## Workflow conditions
To set up a condition, follow the same steps as adding a validator or post-function.
Select the **Condition** option you need and click **Add**.
| **Workflow condition** | **Description** | **Examples** |
| --- | --- | --- |
| ### Limit By Status Condition | Limits the maximum number of issues with a specified status for a single user.
**Configuration**
Specify the maximum number of issues with a specified status allowed per user. |  |
| ### Has Attachments AM Condition | Checks whether an issue has attachments. |  |
| ### Has Links AM Condition | Checks whether an issue has links. |  |