Fields Required Condition & Validator
Field Required Validator (classic) vs. Fields Required Validator (Workflow Building Blocks)
Jira's built-in Field Required Validator makes sure fields aren’t empty during a transition, including the Create issue transition. But here’s the catch: it only works when there’s a transition screen.
The Problem
Let’s say you need an attachment before moving to the next status. If you add the attachment in the Issue View and then try to transition the issue, Jira’s validator won’t recognize it. It expects the attachment to be added during the transition. If there’s no transition screen with the Attachment field, the validator blocks the transition.
The Solution
You have two choices:
Add a transition screen with the necessary fields.
Use a better validator. That’s where our Fields Required Validator comes in.
Our validator checks the entire issue state—not just what’s entered during the transition. This means it recognizes fields filled before the transition, not just during it.
Why Use Fields Required Validator?
Works for arrays (e.g., Attachments, Fix Versions, Components, Comments)—ensuring they have at least one entry.
Validates up to ten fields in one go.
Checks the whole issue state, not just the transition screen.
Supports custom validation messages with Jira Expressions.
Lets you validate that the related issues are added: Children, Sub-tasks, Stories and Linked Issues.
Last updated