About Workflow Building Blocks for Jira

Unlock Jira’s full workflow power—create custom logic, advanced rules, and multi-step tasks effortlessly with Workflow Building Blocks.

Workflow Building Blocks’ app mission is to unlock the power of Jira Expressions for everyone—not just scripting experts. Our app combines ready-to-use, no-code tools with advanced Jira expression capabilities, giving admins both simplicity and full control over workflows. Whether you are an everyday Jira admin or a power user, you can create sophisticated conditions, validators, and post-functions with minimal effort—without writing a single line of code.

Wizard-Like Conditions and Validators

Workflow Building Blocks provides a set of wizard-style conditions and validators designed to simplify workflow management. These tools allow you to extend Jira workflows in a user-friendly way, requiring no advanced knowledge to get started. You can take full control of transitions by limiting their visibility or adding conditions that must be met for a transition to succeed.

Ultimate Validator configuration examples for enforcing mandatory fields conditionally.

Workflow Validators

• Ultimate Validator - Compose highly customized validators visually using the UI

• Linked Issues Validator - Ensure related issues (linked issues, sub-tasks, stories, children or parent) are in the correct state before allowing a transition.

• Dates Compare Validator - Compare two date fields with flexible offsets.

• Fields Required Validator - Checks whether a field has been filled in either during or prior to the transition.

Workflow Conditions

• Ultimate Condition - Compose highly customized conditions visually using the UI.

• Linked Issues Condition - Ensure related issues are in the correct state before a transition.

• Dates Compare Condition - Compare two date fields with flexible offsets.

• Fields Required Condition - Checks whether a field has been filled in either during or prior to the transition.

Jira Expression Preview

Each wizard provides a Jira expression preview, allowing you to see how Workflow Building Blocks constructs the underlying logic. This preview is a valuable learning tool, enabling admins to understand and create Jira expressions more confidently while gaining insight into transition requirements.

Linked Issue Validator configuration example with a preview of the generated Jira Expression.

Jira Expression Conditions and Validators

For advanced use cases, Workflow Building Blocks offers full support for Jira expression-based conditions and validators. The app includes an advanced Jira expression editor that provides suggestions, syntax highlighting, validation, and real-time feedback, making it easier to write complex expressions correctly.

• Jira Expression Validator

• Jira Expression Condition

Jira Expression Validator configuration with expression editor and custom validation message field

Post-Functions Now Available

Workflow Building Blocks now includes ready-to-use post-functions, expanding your automation capabilities beyond conditions and validators. These tools allow you to execute complex, multi-step actions with minimal configuration.

• Transition Work Items – Automatically transition the current issue or related issues (parent, child, or linked) to the next available status in the workflow after a transition.

• Edit Work Item – Automatically modify issue fields after a workflow transition and copy field values from the parent issue, up to two levels up in the hierarchy.

Transition Work Item post function configured to automatically transition the parent when all child issues are Done, using sibling status preconditions.

With post-functions, admins can save time, reduce errors, and maintain consistent workflows, empowering teams to follow automated processes without coding.

Top 10 Use Cases for Workflow Building Blocks

1. Prevent closing issues with blocking links – Prevent closing an issue if it has an “is blocked by” linked issue.

2. Epic/task dependency enforcement – Prevent closing an epic until all its tasks are completed and enforce story transitions only when the epic is in progress.

3. Sub-task status validation – Validate the status category of sub-tasks for specific types.

4. Date-based transitions – Allow transitions based on dates set in the future or past, or by comparing two date fields with offsets in weeks, days, hours, or minutes.

5. Field-based conditions – Make fields mandatory or conditionally required based on other field values, resolution, or issue type.

6. Assignee/reporter validation – Compare two different fields, e.g., ensure the assignee is different from the reporter.

7. Sprint & version validation – Validate that an issue is part of an active sprint and ensure it is not associated with released versions.

8. Restrict actions to specific users – Reserve the privilege of closing issues solely for their creators and control issue creation based on project role.

9. Edit multiple fields automatically – Automatically edit multiple fields in an issue after a workflow transition.

10. Automated issue transitions – Automatically transition the current issue or related issues (parent, child, or linked) to the next available status in the workflow after a transition.