Draft CRA Article 14 reports and notifications inside Jira and Jira Service Management — staged deadlines tracked from the correct start point, and your incident data never leaves your tenant.
Support & FAQ
Installation, permissions, data location, KEV snapshot, deadlines, plans, and who is responsible for what.
Documentation
How to use the Readiness Check, Reporting & Notifications, and the Vulnerability Register & Drills.
Privacy policy
How the app handles data — built to the Runs on Atlassian model with no external egress.
Terms of use (EULA)
License terms, disclaimers, and limitations for using the app.
These pages practice what the app promises: static HTML only — no cookies, no analytics, no external fonts or scripts, nothing loaded from third parties.
Guides on CRA Article 14 reporting
- CRA incident reporting in Jira: mapping Article 14 to your tickets Where the report is actually born, the two final-report clocks, and what to capture in tickets before September.
- The CRA Article 14 vulnerability report: what to file, and when the clocks really start The actively-exploited path in depth — including the pending final-report clock that waits for a fix.
- 24-hour reporting under the CRA: what the early warning actually requires A signal, not an analysis — and the two decisions that actually consume the 24 hours.
- Choosing a CRA compliance tool: build, buy, or work where your tickets live A comparison framework with the evaluation questions that separate the field, bias declared.
- ENISA's Single Reporting Platform: what is settled, what isn't Three layers of certainty, and how to prepare without hard-coding a moving target.
Free checklist (PDF): CRA Article 14 Reporting Readiness Checklist — product inventory (including legacy products), reportability judgment, the staged deadlines with both start points, user and upstream notices, and single-reporting-platform preparation. Source-referenced; not legal advice.
Support contact: support@complydraft.com
Response target: within 2 business days.