Skip to content
Menu

Which EU incident reports are due, by when and to whom.

GDPR, NIS2, DORA and CRA, on the Jira work item. And the record of what was sent.

One email when it’s live, then we delete your address. Privacy

Inside Jira. Privacy first. No servers. It writes only its own reminders.

The Dueline panel on a work item qualified for GDPR, NIS2 and CRA, aware Sat 31 Oct 22:07 (Europe/Riga). Its first line says who qualified it and when, with “Updated just now” and Recalculate in its top right corner. Its head says Due soon: CRA early warning of an exploited vulnerability due in 20 h. The reports are grouped by rule, each group naming where it goes, how, and what to have ready, for a company in Denmark. GDPR, to the Danish Data Protection Agency (Datatilsynet), through its portal with Virk.dk and MitID: the notification to the supervisory authority Due in 2 d 20 h, the communication to the people affected with no deadline, the breach register Recorded in Dueline. NIS2, to the Danish Agency for Societal Security (SAMSIK): the early warning Sent, with a Correct button, the incident notification Due in 2 d 20 h, the intermediate report On request, the final report Waiting for the incident notification. CRA, to the ENISA Single Reporting Platform: the early warning of an exploited vulnerability Due in 20 h, the vulnerability notification Due in 2 d 20 h, an intermediate report On request, the final report Waiting for a fix, with a Fix available button. Nothing is late. The small print says the assessment is yours, that it is not legal advice and that Dueline sends nothing, and that reminders come as comments on the work item and may be a few minutes late: the clock is what counts. The panel ends with an Open in Dueline link.
The Dueline panel on a work item, reports grouped by rule.

Qualify once, the clocks start

One question per rule you switched on, with the article’s test beside it, and when you became aware.

The Qualify this work item dialog: when you became aware, 26 Oct 2026 at 09:00, in the Europe/Riga time zone. GDPR is on, with “The risk to people is high: Art. 34 asks that they are told too” on under it. NIS2 is on. DORA is on, with the time it was classified as major, 26 Oct 2026 at 10:30. CRA is on, with “An actively exploited vulnerability” chosen over “A severe incident that affects the product’s security”. Cancel and Qualify buttons.
The Qualify dialog, from the Dueline panel on a work item.

Every report shows what the article asks for

The article’s contents for that report, and a link to the rule on EUR-Lex.

The Dueline panel’s table with the GDPR notification to the supervisory authority opened, under the Danish Data Protection Agency’s details: Due Thu 29 Oct 09:00, Late by 2 d 7 h with “Give the reasons for the delay” and a Record as sent button. Under it “The article asks the report to hold”: the nature of the breach, the categories and approximate number of people and of records concerned, the data protection officer’s or another contact point, the likely consequences and the measures taken or proposed; the note that a notification later than 72 hours comes with the reasons for the delay; and a link to General Data Protection Regulation (EU) 2016/679.
A report opened in the panel: the arrow beside its name.

DORA’s weekend rule, shown

A deadline on a weekend shows the later noon the rule allows, beside the strict time.

The Dueline panel on a DORA work item, aware Fri 23 Oct 21:30, with “Updated just now” and Recalculate in its top right corner: DORA initial notification is late by 5 d. The report goes to Finanstilsynet, reported on Virk.dk with a MitID Erhverv login. The initial notification is due Sat 24 Oct 02:30, or by Mon 26 Oct 13:00, Late by 5 d with “Give the reasons for the delay” and a Record as sent button. The intermediate report is Waiting for the initial notification, the final report Waiting for the intermediate report. Under the table, the small print, the note about reminders, and the note that Dueline does not move a deadline for a bank holiday, so its time may be earlier than the law allows, never later; then an Open in Dueline link.
A DORA report due on a Saturday: its strict time and “or by” Monday noon.

Record what was sent

When, by whom and the reference the authority gave. Never rewritten.

The Record notification to the supervisory authority as sent dialog: sent 28 Oct 2026 at 10:15, the optional reference 2026-1042, the note “Add the authority’s case or reference number, not a person’s name. Kept with the record”, Cancel and Record buttons.
Record as sent, on any report.

Every incident, in one list

Late first, with each one’s next deadline, across the spaces you choose. Filter it, copy a link to it, download it as Excel or CSV.

Dueline’s register under Apps: the scope Spaces with ITO and SECOPS chosen, “12 incidents” with 9 Late and 3 Due in 24 h, Copy link, Download Excel and Download CSV buttons, and Space, Rule and State filters. The table lists each work item with its rules, status and next deadline, what is late and how many reports were sent, and its space, the late ones first: ITO-17 DORA, ITO-3 GDPR, NIS2, CRA, SECOPS-164 NIS2, ITO-2, ITO-22, ITO-29, ITO-30, ITO-12 and ITO-13, then ITO-14, ITO-9 and ITO-10 Due soon, and the line “12 incidents in ITO, SECOPS” with the age and Recalculate over the filters.
The register, under Apps › Dueline.

Due next, on a dashboard

The incidents with a report due, late first, on any Jira dashboard. Each person sees only the work items they may browse.

The Due next gadget: a grey first line, “12 incidents have a report due · in every space”, then a table of work item, status and next report, the late ones first (ITO-17, ITO-3, SECOPS-164, ITO-2, ITO-22, ITO-29, ITO-30, ITO-12 and ITO-13, Late), then ITO-14 Due soon, each with its next report and date, a Show 2 more button, and a footer with the age and an Open in Dueline link.
The Due next gadget, added to a dashboard like any other.

Admins choose the rules

The rules that apply, your country, DORA’s weekend rule and the response team.

Dueline settings: the “Where Dueline shows up” card first, then GDPR, NIS2, DORA and CRA switched on, each with its hint under it; the country of the main establishment, Denmark; the DORA weekend rule and the NIS2 trust service provider switches off, and the financial sector not picked; the Reminders section with “Remind the response team” on; the response team’s people and groups pickers, empty; a Save button and the line “Inside Jira. No servers. It writes only its own reminders.” with a Privacy policy link.
Dueline settings, under Jira settings › Apps.

Four rules, one clock

  • GDPR: within 72 hours

    To the supervisory authority after a personal data breach, and to the people affected when the risk is high.

  • NIS2: within 24 hours, 72 hours, one month

    An early warning, an incident notification and a final report to the national CSIRT or authority.

  • DORA: within 4 hours, then 72, then one month

    An initial notification, an intermediate report and a final report, on the authority’s templates.

  • CRA: within 24 hours, 72 hours, then the final report

    For an exploited vulnerability or a severe incident in a product, on ENISA’s single reporting platform.

Work out your deadlines, free →Every report and its deadline →

From the work item to the record

  • Qualify the work item

    One question per rule you switched on, and when you became aware. That starts the clocks.

  • See what is due

    Each report, when, in how long, and who it goes to, with what the article asks it to hold.

  • Report it yourself

    Dueline sends nothing. You file with the authority, in its own form.

  • Record what was sent

    When, by whom and a reference, kept for the work item and never rewritten.

What stays with you

  • The assessment is yours

    Whether a breach or an incident must be reported is your call. Dueline asks, with the article’s test beside the question.

  • National law may be stricter

    NIS2 is a directive, and a country can ask for more than the EU rule. Dueline shows the EU rule.

  • Dueline files nothing

    No report leaves Jira. You send it, then record it.

  • It is not legal advice

    It works out dates from the texts of the rules as read on EUR-Lex on 28 October 2026, each linked.

What you get

On the work item

Qualify
One question per rule that applies, with the article’s test beside it, and the time you became aware.
Reports by rule
Each one due, with its deadline, how long is left and who it goes to.
What the article asks of each report
Its contents from the article, and a link to the rule on EUR-Lex.
Record as sent
When it was sent, by whom, and the reference the authority gave.
Reports that wait
A report that runs from an event says which one: a fix, or the incident handled.
Late says so
A report past its deadline turns red and points to the reasons for the delay the rule asks for.
Reminders
A comment on the work item, mentioning the response team, when a quarter of the time is left and when a report is late. It may come a few minutes late.
Correct an entry
Fix a time or a reference. The original stays in the record.

Across your spaces

The register
Every qualified incident in one list, late first, with its next deadline. Filter it, copy a link to it, download it as Excel or CSV.
Due next, on a dashboard
The incidents with a report due, late first, in the spaces you choose. Each person sees only the work items they may browse.

For Jira admins

The rules that apply to you
Switch on GDPR, NIS2, DORA or CRA. Only those are asked.
Your main establishment
The country sets the time zone a weekend is read in.
DORA’s weekend rule
Shows the later noon the rule allows, unless you are an entity it never applies to.
The response team
People and groups who may qualify and record. Jira admins always may.
Kept on Atlassian
The record is append-only: a correction is a new entry.
Nothing sent
No external service. The only thing it writes to a work item is its reminder comment.

Dark mode, too

Every Lineset app follows your Jira theme, light or dark.

The same Dueline panel in Jira’s dark theme: the head Due soon, CRA early warning of an exploited vulnerability due in 20 h, and the reports grouped by GDPR, NIS2 and CRA, for Denmark, on a dark background, the NIS2 early warning Sent.

Secure and private

Inside Jira
It runs where your Jira runs, and nothing leaves your site.
No servers
None of ours, and no external services: nothing is sent anywhere.
One write
Its own reminder comment on a work item, and never a field.
Reads as you
Your own Jira permissions apply to what it reads.

Built on Atlassian Forge. No tracking. What it reads and stores →

Pricing

Free up to 10 users

The price per user drops as you grow

  • Billed by Atlassian
  • Every feature on the free tier
  • 30-day free trial

Questions

Does Dueline send the reports?

No. It shows which reports are due, when and to whom, and keeps the record of what you sent. You file with the authority yourself, then record it on the work item. Nothing leaves Jira.

How to file a report and record it as sent →

Does Dueline decide whether a report is due?

No. Qualifying a work item is your assessment: Dueline asks one question for each rule you switched on, with the article’s test beside it, then starts the clocks. National law may be stricter than the EU rule, as NIS2 allows, so check your country’s too. Dueline is not legal advice.

How to qualify a work item, step by step →

Does it move a DORA deadline off a weekend?

It shows the later time the rule allows, noon of the next working day, beside the strict deadline. Only weekends are built in, read in your country’s time zone: bank holidays are not, so a deadline Dueline shows can be earlier than the law allows, never later. A competent authority may rule the move out for a significant entity. For credit institutions, central counterparties, trading venues and NIS2 entities the rule does not move the initial and intermediate reports: an admin switches that on in the settings.

What does it cost?

Free up to 10 users, then billed per user by Atlassian, with a 30-day free trial. Every feature is on the free tier. The price per user drops as you grow, and the Marketplace listing shows the exact cost for your site.

All questions →Doing it with Jira’s own tools? Step-by-step guides →

Know what is due

One email when it’s live, then we delete your address. Privacy