GuardPulse for Jira
Block Done until blockers are closed. A workflow validator for Jira Cloud by PuzariCloud. Runs on Atlassian.
What it does
GuardPulse adds the workflow validator Blockers, sub-tasks and links are done (GuardPulse). Put it on a transition (usually Done) and the transition fails until every check you turned on passes. The error tells the user which issues are still in the way.
| Check | Blocks the transition while… |
| Linked issues are done | an issue linked with the link types and sides you pick (for example is blocked by) is not done |
| Sub-tasks are done | any sub-task is not done |
| Child issues are done | any child issue (issues in an epic, or children set through the Parent field) is not done |
| Required link exists | the issue has fewer than N links of the chosen types |
| Has attachments | the issue has fewer than N attachments |
Set it up
- Go to Settings > Work items > Workflows (or your project's workflow) and edit the workflow.
- Select the transition, for example Done. Under Validate details choose + and pick Blockers, sub-tasks and links are done (GuardPulse).
- Turn on the checks you need. For linked issues, pick the link phrases that mean "blocked". is blocked by is selected for you.
- Choose what counts as done: any status in the green Done category, extra statuses such as Won't do, or both.
- Optional: write your own message per check. Placeholders:
{keys} (the issue keys, up to 10 plus "and N more"), {count}, {min}, {links}.
- Type an issue key in Test on an issue and press Would it pass?. GuardPulse runs the rule on that issue and shows the result. Nothing is changed.
- Press Add (or Update), then Update workflow.
Example error: Close the blocking issues first: APP-12, APP-15. Finish the open sub-tasks first: APP-20. Turn off "Show every failing check" to show only the first one.
Good to know
- Works in company-managed and team-managed projects, in the new workflow editor.
- Pick link sides as they read for the issue being moved. "is blocked by" means: this issue is blocked by the linked one. "blocks" would check the issues this one blocks.
- If a user cannot see a linked issue, GuardPulse skips it rather than revealing it.
- On the create transition, sub-tasks, children and attachments do not exist yet and are not checked.
- Each check lists at most 10 keys, then "and N more".
- Before uninstalling GuardPulse, remove its rules from your workflows: Jira treats validators of an uninstalled app as failed.
- The rule is a Jira expression that Jira evaluates during the transition, so it adds no noticeable delay.
Security and data
GuardPulse runs on Atlassian Forge and makes no calls outside Atlassian. It has no functions, no servers and no storage of its own: the validator settings (link type IDs, status IDs and names, your messages) are saved by Jira inside the workflow. See the privacy policy.
Support
Email support@puzaricloud.in. We reply within two business days.