Jira Cloud · Atlassian Forge
A living map of what you have and how ready it is — inside Jira.
Readiness Map turns the systems, components, and dependencies you track in diagrams and spreadsheets into a living map inside Jira that never writes to Jira — a registry and provenance record, not another drawing that goes stale.
Coming soon to the Atlassian Marketplace — we'll let you know the moment it's live.
See it in action
Inside a box
Every component opens an inspector beside the diagram — what it is, what it connects to, its live Jira position, and the notes it carries. It's where you link a ticket, add a connection, or confirm a box complete.
The problem
Readiness lives in diagrams that drift and spreadsheets no one trusts. Drawing tools give you a picture; none of them give you a record you can rely on — what each thing is, where it came from, and how ready it is across stages.
What Readiness Map does
Readiness Map keeps a registry of your components and their readiness across the stages you define, with dependencies and provenance as first-class data. The map is just a view of that record — so it's always current, traceable, and auditable.
What you get
Every component is held once in a register, with its ID, what it is, and where it's used. A component that appears on several flows is one entry, not several, and every diagram is drawn from that register, so the picture can't drift from the record.
Lay each flow out in columns you name, connect the boxes, and keep reports, notifications, and monitors in a band beneath the diagram so they don't clutter it. Nothing is saved until you confirm where a box landed.
Each component is matched to its Jira issues through Jira's own Components field, so every box shows its live work. See every linked issue in one list with fix version, status, and assignee, and narrow the counts to a single delivery version.
A component counts as complete only when every Jira ticket against it is closed and someone has confirmed it. A hollow tick means Jira is clear but nobody has confirmed; a solid tick means both; an exclamation mark means it was confirmed and then the work changed.
Unnamed upstream systems, inferred connections, and ambiguous IDs are recorded, not guessed. Things outside the register are drawn dashed, and notes hold the findings, questions, and blockers that don't have a Jira ticket yet.
Download a single, self-contained HTML file with every flow's diagram, purpose, business rules, and components, plus the register. It opens offline and prints cleanly to PDF. Notes stay in the app.
Download the whole workspace as one file and restore it whenever you need to, including onto another Jira site. You can limit restoring to a Jira group, and nothing destructive happens on a single click.
Not a ticket, not a field, not a component. Readiness Map reads Jira under your own permissions, so it only sees issues you can already see, and everything you change is kept in the app.
Forge-native, and the app declares no outbound network permission at all. Your workspace lives in Forge storage inside your own Atlassian site, so there's no sub-processor for your security team to review.
Built to pass a security review
Readiness Map is a Forge app with no external network calls — there's no server of ours in the path, no sub-processor, and nothing for your security team to approve beyond Atlassian itself.
More detail on the security & data handling page.
Pricing
Free during early release. If paid plans are introduced later, existing installs will get clear, advance notice.
We're finishing the Marketplace listing. Tell us about your Jira and we'll let you know the moment it's live.