About Workflow Building Blocks for Jira

Workflow Building Blocks offers ready-to-use, no-code conditions and validators to address the most common needs when constructing a workflow. For advanced use cases, the app provides Jira expression-based conditions and validators capable of meeting almost any organizational requirement.

Wizzard-like conditions and validators

Conditions and validators in the form of wizards allow for a user-friendly way to extend the workflow. You don't need any advanced knowledge to start using them. Take control of transitions by limiting their visibility or adding conditions that must be met for the transition to succeed.

Workflow validators provided by Workflow Building Blocks for Jira:

• Ultimate Validator

• Linked Issues Validator

• Dates Compare Validator

• Fields Required Validator

Workflow conditions:

• Ultimate Condition

• Linked Issues Condition

• Dates Compare Condition

• Fields Required Condition

Jira expression preview

The Jira expression preview feature offers you a sneak peek under each wizard, revealing how the application constructs expressions internally and showcasing the exact conditions required for transitions. This preview serves as a valuable tool for learning Jira expression syntax and empowering you to create your own sophisticated conditions with ease.

Jira expression conditions and validators

The Workflow Building Blocks application allows you to create your own conditions and validators. Within the app, you'll find an advanced Jira expression editor. The editor provides suggestions and validates syntax, making expression writing much easier.

Provided by Workflow Building Blocks for Jira:

• Jira Expression Validator
• Jira Expression Condition

What can I do?

Discover what you can achieve with our app:

• Prevent closing an issue if it has an “is blocked by“ issue linked

• Prevent closing an epic until all its tasks are completed

• Validate the status category of sub-tasks for a specific type

• Enable story transitions within an epic only when the epic is in progress

• Allow transitions based on dates set in the future or past

• Compare two date fields with an offset in weeks, days, hours, and minutes

• Reserve the privilege of closing issues solely for their creators

• Make fields mandatory based on various criteria, such as resolution or issue type

• Compare two different fields, for example, ensure that the assignee is different from the reporter

• Validate that an issue is part of an active sprint

• Control issue creation for specific types based on the user's project role.

Check out more examples in use cases page.