Explain each issue
See ready, review, blocked, or exempt status with specific reason codes and remediation guidance.
Jira Cloud workflow quality
Catch missing evidence before work moves forward.
Gatehouse is an explainable issue-readiness quality gate for teams that need consistent standards without another opaque scoring system.
The problem Gatehouse solves
Issues often move into implementation or release with acceptance criteria, evidence, ownership, or required links still missing. Review becomes inconsistent, blockers surface late, and teams waste time reconstructing what “ready” was supposed to mean.
One policy, three useful surfaces
Prioritize the project
Review and filter readiness across a bounded project queue instead of opening issues one by one.
Enforce when appropriate
Attach the optional workflow validator to selected transitions while keeping policy configuration visible to project admins.
See Gatehouse in Jira
Project readiness overview
Review the queue, filter by status, and focus on the issues that need attention.
Issue-level explanation
Understand exactly why an issue is ready, needs review, or is blocked.
Project policy settings
Configure deterministic requirements without exposing customer content outside Forge.
Designed for a small data footprint
Runs on AtlassianBuilt entirely on Forge with no Sallux-operated backend or external egress.
No issue-content storageIssue fields are evaluated transiently; only project policy and its update timestamp are stored.
No Jira write scopeGatehouse reads configured fields and evaluates transitions without modifying customer issues.
Marketplace launch in preparation
Gatehouse is completing Atlassian Marketplace listing and review preparation. Contact us if you would like launch updates.