Linked Issues Condition & Validator
How to setup Linked Issues Condition and Linked Issues Validator
Both Linked Issues Condition and Linked Issues Validator help ensure that related issues (linked issues, sub-tasks, stories, children or parent) are in the right state before allowing a transition to proceed. If theyโre not, the transition is blocked. Simple as that!

โ๏ธ Configuration Options
Relation
Pick what kind of issue relationship you want to check:
Linked Issues โ Regular issue links like "blocks" or "relates to."
Sub-Tasks โ Checks the issueโs sub-tasks.
Stories โ Validates an Epicโs child issues (excluding sub-tasks).
Children โ Checks both child issues and sub-tasks. Works when youโve set up multiple hierarchy levels.
Parent โ Validates the parent issue.
Link Types (optional)
If using Linked Issues, you can filter by specific link types. Links have a name and direction (e.g., "relates to" might have incoming and outgoing links).
Issue Types (optional)
Only need to check specific issue types? No problemโjust set a filter! Great for:
Only certain issue types need to be completed before transitioning.
You want to enforce having a child of a specific issue type.
Require At Least One Issue
Checks if at least one issue exists that matches the selected relation (and previous filters). If not, the validator fails.
Status Category and Statuses
Best Practice: Use Status Categories instead of specific statuses to check if related issues are completed.
Why? Status names can change over time, but categories (To Do, In Progress, Done) stay consistent.
Example: Instead of checking for "Resolved," check if the issue is in the "Done" category.
Override Validation Message (Validators Only)
This setting allows you to customize the validation message instead of using the default one generated based on your selected settings. You can also use Jira expression syntax to make it more dynamic.
Learn more about writing validation messages
Use cases
Last updated