NexaForge Labs · Jira Cloud · Company-managed workflows
Workflow Guard for Jira
Simple guardrails for Jira workflows.
Block or hide transitions with focused checks for related work, attachments, versions, sprints, due dates and relationship counts. Configure guided forms and readable summaries without writing expressions.
Marketplace publication is in preparation. The app is not yet publicly available.
Eight checks. Two ways to enforce them.
Validators block a transition with a configured message. Conditions hide a transition until its requirement passes.
Choose a guard
Common workflow requirements, in guided forms.
- Linked Work Status
- Subtask Status
- Parent Status
- Existing Attachment Count
- Fix Version State
- Sprint State
- Due Date Guard
- Relationship Count
Select a transition, add Workflow Guard under Validate details or Restrict transition, configure its requirements and publish the workflow. The guide explains empty collections, missing parents, visibility limits and native transition-screen behavior.
Data flow
Configuration stays in Jira.
Atlassian hosts the Forge interface and Jira expression evaluation. The app has no external application backend, customer-data database or third-party analytics. It counts existing attachments without retrieving file contents.
Read privacy and data-flow detailsBefore using it
Check scope and visibility.
This release supports company-managed Jira Cloud workflows. Linked checks see only links available to the transitioning user. Team-managed workflows, post functions, custom scripts and general automation are outside its scope.
Before uninstalling, remove all app conditions and validators and publish the workflows. Retained rules can block transitions.
Pricing and availability
Planned as a Paid via Atlassian app with standard billing. Final prices, trial availability and installation will be shown on the Marketplace listing after approval. No purchase is available on this website.