EA Sphere for Jira
Your systems, their dependencies and your continuity plans, in one place in Jira.
When a system fails, the first minutes turn on two questions: what else is affected, and who needs to be told. EA Sphere answers both from records your teams keep alongside their work in Jira.
It maps your systems, servers, interfaces and facilities and the dependencies between them, shows the impact of a change before the work begins, measures each degradation against recovery objectives, and generates the continuity package and tabletop exercises from the same live records.
Four capabilities, one map
Enterprise architecture mapping
Systems, servers, interfaces and facilities with owners, recovery tiers, dependencies, data flow and business functions, explored on a dependency map up to four levels deep.
Change and impact logs
Reference systems from any Jira work item to see downstream impact, change collisions and freeze conflicts before work begins. Every change to a record is logged.
Degradation management
Outages and slowdowns recorded with stages, updates and incident work items, measured against recovery time objectives, with notices to audiences you can restrict by Jira group.
Business continuity management
The contact sheet, recovery sequence and continuity package generated from live data, tabletop exercises written from your own map, and briefings for every team and incident role.
Features
Dependency map
Put any record at the centre and choose adjacent, downstream or upstream, one to four steps deep. Data flow direction is shown on every link, with a count of open work on each record.
Catalog and recovery tiers
Records carry owner, contacts, lifecycle dates, data classification and recovery tier. Tiers set RTO, RPO, maximum tolerable downtime, availability target and review interval once, and every record inherits them.
Work items and impact
The EA Sphere panel on each Jira work item lists the systems it changes, delivers or retires and what sits downstream of them. Delivers and Retires update the catalog when the work is done.
Degradations and notices
Stages, timestamped updates, root cause and mitigation, measured against the tier’s objectives. Notices are composed from the degradation, restricted to sender groups and recorded when sent.
Continuity documents
Contact and escalation sheet, recovery sequence, cyber incident sheet and the full package, generated when opened and stating how current and how verified the data is.
Tabletop and recovery exercises
Scenarios written from your own map, a facilitator view with developments, decisions and gaps, an after-action report and follow-up work items. Recovery exercises are timed against objectives.
Learning and acknowledgments
Briefings for each team and incident role drawn from the records, with knowledge checks, acknowledgments and coverage tracked by Jira group.
Dashboard, calendar and reports
One page of drillable snapshots, a calendar of degradations, windows, exercises and lifecycle dates, and eight reports that filter and export.
Administration
Tiers, reference lists, freeze windows, audiences, sender groups and templates are maintained by Jira administrators, with every permission checked on the server.
Sample company
Load a complete sample organization to explore every feature before you enter your own records, and remove it in one step.
Security and data
Runs on Atlassian
EA Sphere is an Atlassian Forge app. Its functions run on Atlassian-hosted compute and its data is held in the Forge storage allocated to your Jira site, following your site’s data residency.
No external calls
The app declares no external permissions, loads nothing from outside Atlassian and uses no analytics or tracking.
Access from Jira
Access follows Jira permissions and groups. Settings and bulk operations require Jira administrator rights, checked on the server.
Renevell as processor
Renevell processes your data only to provide the app, with Atlassian as its sub-processor. Renevell’s staff have no access to the records you keep.
For security and procurement reviews: the full security and data handling statement, privacy policy, terms of service and data processing addendum.
Pricing
Sold through the Atlassian Marketplace and billed by Atlassian with your Jira Cloud subscription, priced by the number of users on your Jira site.
| Licensed Jira users | Price |
|---|---|
| 1–10 | $25 a month in total |
| 11–100 | $5.00 per user a month |
| 101–250 | $3.75 per user a month |
| 251–1,000 | $2.00 per user a month |
| 1,001–2,500 | $1.10 per user a month |
| 2,501–5,000 | $0.65 per user a month |
| 5,001–10,000 | $0.40 per user a month |
| Above 10,000 | $0.30 per user a month |
Up to 10 users is a flat monthly price, not per user. Annual subscriptions cost ten times the monthly price, and a 30-day free trial is available through the Atlassian Marketplace.
Larger organizations and public-sector purchasers can contact us about terms.
Demo and pricing