Rules that show their working.
When something happens in Jira, check what you care about and act: transition, assign, comment, create, link, log work. Test a rule before it goes live, and read exactly what it did every time it ran.
The real module, running right here.
Working software on sample data — the same interface that renders inside Jira. It plays a short tour when it comes into view; click anywhere in it to take over.
The issue on the right is made up. Everything that decides what happens to it is the real thing: this page runs the app's own rule engine, in the dry mode the Test run button uses inside Jira, and the log is what that engine really writes. Change the issue and watch each condition answer. Installed in Jira the only difference is that a run is not a dry one — project administrators write the rules for their own projects, every change is recorded as Bastion Helix, and each run keeps the log you see here.
Built for the job, not the brochure.
Triggers
Issue created, updated, transitioned, assigned, commented, linked; work logged; on a schedule; email received; timesheet and budget events.
Conditions
Fields and how they changed, JQL, people, hours logged and budget figures — each one answers yes or no in the log.
Actions
Transition, assign, edit fields and labels, comment, create issues and sub-tasks, link, log work, notify and change watchers.
Act beyond the issue
Point an action at the issue’s parent, its sub-tasks, its linked issues, or everything a JQL search returns.
Test run first
The Test run button runs the real rule engine in a dry mode, so you see what would happen before anything does.
Owned by the project
Project administrators write the rules for their own projects. Every change is recorded in Jira as Bastion Helix, and the rule’s history says why.
Three steps from install to answer.
Pick a trigger
Choose what starts the rule, or start from a ready-made one such as escalating urgent bugs.
Add conditions and actions
Say what must be true, then what should happen and to which issues.
Test, then switch on
Dry-run it against an issue you choose, read the log, and turn it on when it does what you meant.
Inside Atlassian, with Jira’s rules.
Rules run on Atlassian’s compute, not ours. What a rule changes is written to Jira as Bastion Helix, so nothing it does is anonymous. What “never leaves your instance” means →
- Project admins write rules for their own projects
- Every run keeps a log of each condition and action
- No rule can delete an issue — there is no such action, and nothing in the app’s code does
- Email received is a trigger, so mail can start a rule
Straight answers.
What can a rule change?
Transitions, comments, fields, labels, links, watchers, logged work and new issues and sub-tasks. It cannot delete an issue: there is no such action, and nothing in the app’s code deletes one.
Who can create rules?
Project administrators, for their own projects.
Can I see why a rule did something?
Yes. Every run keeps its log — which trigger fired, how each condition answered and what each action did — and the change itself is recorded in Jira as Bastion Helix.
Guides and articles.
Turn a support address into Jira issues with Cloudflare Email Routing
Forward a support address on your own domain into Jira, so each new message becomes an issue and each reply lands as a comment — without giving any app a mailbox.
Read the guide →See Claude Code spend per person, team and Jira issue
Point Claude Code’s own telemetry and a GitHub webhook at Workforce Intelligence, and see what AI coding costs — per person, per team, and per Jira issue it helped build.
Read the guide →Earned value for Jira projects, in plain English
Spent 48% of the budget — is that good? Earned value answers by comparing what you spent with what that money was supposed to buy. Here is the whole idea, with one worked example.
Read the guide →Be first in when it opens.
One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.
Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.