Draw it where the work lives.
A flowchart editor on every project: drag, resize, connect and label, keep the last thirty versions, and bring your draw.io files in — or take them back out whenever you like.
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.
Drag, resize, connect and label. Export a .drawio file and open it in draw.io, or import one of yours — it never leaves your browser. Installed in Jira, diagrams live on each project and follow its permissions.
Built for the job, not the brochure.
Shapes that mean something
Boxes, rounded boxes, diamonds and ellipses in seven colours — the vocabulary of a process map without a palette of a thousand icons.
Direct manipulation
Drag, resize, connect, label and reverse arrows, with undo while you edit.
Every save is a version
The last thirty versions are kept. Open any of them, or restore it, without losing what came after.
Per project or site-wide
Diagrams belong to a project or to the whole site, so a team’s process map sits next to its issues.
draw.io in and out
Import a .drawio file and it opens as an editable diagram. Export any diagram back to .drawio, so nothing is locked in.
Project permissions apply
Only people who can browse a project can open its diagrams.
Three steps from install to answer.
Open a project
Diagrams sit on each project’s Bastion Helix page, in Jira’s project sidebar.
Draw or import
Start blank, or import a .drawio file you already have.
Save and share
Every save keeps a version; anyone who can browse the project can open it.
Inside Atlassian, with Jira’s rules.
Diagrams are saved in the app’s Forge storage, alongside the project they belong to. Import and export happen in your browser — the file you choose is never uploaded anywhere else. What “never leaves your instance” means →
- Opening a diagram needs permission to browse its project
- Versions keep the last thirty saves
- Import reads uncompressed .drawio files — what recent draw.io saves by default
- Export writes a .drawio file that opens in draw.io
Straight answers.
Can I bring my draw.io diagrams?
Yes. Import a .drawio file into any project and it opens as an editable diagram, and any diagram can be exported back to .drawio. Import reads uncompressed .drawio files, which is what recent versions of draw.io save by default; for an older compressed file, untick Compressed under File → Properties in draw.io first.
Who can see a diagram?
Anyone who can browse the project it belongs to.
Guides and articles.
Bring your draw.io diagrams into Jira — and take them back out
Process maps and architecture sketches are most useful next to the work they describe. Here is how to move draw.io diagrams onto a Jira project without locking them in.
Read the guide →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 →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.