On this page
DORA Desk brings the Digital Operational Resilience Act into Jira. Run the yearly resilience drill on your real Jira screens, classify a real incident as major or not, and never miss the regulator’s 4 h / 72 h / one-month clocks. Every decision and report goes into a hash-chained evidence log the auditor can verify.
The regulator’s clocks, always in sight
Classify an incident as major and the clocks start: the initial notification 4 hours later (24 hours after detection at the latest), the intermediate report 72 hours after it, the final report one month after the last intermediate one. Weekends and your region’s bank holidays follow the rule your authority applies. The Clock wall shows them full screen in the war room.
A drill on your real Jira screens
Pick a scenario — ransomware on the payments gateway is built in — and start the drill. Each inject arrives as a Jira work item assigned to its role: IT, Legal, Communications, the incident commander. People decide by commenting; each decision is on time or late against the runbook’s target.
Major or not — by the rules
The classification panel on an incident asks the questions of Regulation 2024/1772: clients affected, duration, geographical spread, data losses, critical services, economic impact. The answer — major or not, and why — goes into the evidence log with who classified it.
The after-action report writes itself
When the drill ends, the report is ready: decisions on time, the median time to decision, what went late and the findings, as work items. Publish it to Confluence in one click.
Evidence for the auditor
The Evidence tab builds the year’s package — drills, findings and the incidents register — as JSON and PDF, attaches it to a Jira work item and writes its SHA-256 into a hash-chained log. Each item is mapped to DORA, NIS2, ISO 27001 and SOC 2.
Try it in three minutes
Start the demo drill on the Get started tab: ransomware on the payments gateway at 20× speed. You are the incident commander; IT, Legal and Comms are demo participants. Remove demo drill takes it away.
Frequently asked questions
Who is DORA Desk for?
Financial entities under the EU Digital Operational Resilience Act (DORA) — payment and e-money institutions, credit institutions, trading venues — and essential or important entities under NIS2 that run incident response in Jira.
Which DORA deadlines does it track?
The initial notification 4 hours after an incident is classified major (24 hours after detection at the latest), the intermediate report 72 hours after the initial notification, and the final report one month after the last intermediate report — with the weekend and bank-holiday rule of RTS 2025/301 Art. 5.
How does a drill work?
Each inject of the scenario arrives as a Jira work item assigned to its role, with the clock running. People decide by commenting on their inject; the decision counts from the comment's minute, on time or late. When the drill ends, the after-action report is written for you.
Does any data leave Atlassian?
No. DORA Desk declares no outside host and carries Atlassian's Runs on Atlassian badge. Everything it keeps is in Forge storage inside your site; see the privacy policy.
What does the auditor get?
A yearly evidence package — drills, findings and the incidents register — as JSON and PDF attached to a Jira work item, with its SHA-256 in a hash-chained evidence log, mapped to DORA, NIS2, ISO 27001 and SOC 2.
Get DORA Desk
Free up to 10 users. Install it from the Atlassian Marketplace.