Documentation
Start with the lessons: qualify a work item, read its deadlines and record what you sent. Then go further, and look up how deadlines are counted and what Dueline stores.
Start here
- Qualify a work item
Qualify a work item in Jira step by step: open Dueline’s panel, say when you became aware, switch on each rule it meets and start the reporting clocks.
- Read the deadlines
Read a qualified work item’s reports in Jira: when each is due, how long is left, who it goes to and what the article asks it to hold.
- File the report and record it as sent
File a report with the authority yourself, then record it as sent in Dueline with the time and the authority’s reference, and correct it if needed.
Go further
- Find Dueline and set it up
Where Dueline appears in Jira Cloud once installed: the work item panel, the register, the gadget and the settings page, and the first steps for an admin.
- The response team
Who may qualify a work item and record a report: Jira administrators always, and the people and groups an admin adds. Everyone else sees the clocks.
- Settings
The site-wide settings a Jira admin can change: the rules that apply, the country, DORA’s weekend rule, trust service providers, the response team.
- Where to file, by country
For GDPR, NIS2, DORA and CRA: the authority each country’s reports go to, where and how to file, and what to have ready first.
- The register and the gadget
Dueline’s register under Apps and its Due next gadget for a dashboard: every qualified incident across your spaces, the late ones first, with downloads.
- Reminders
The comments Dueline adds to a work item when a quarter of a report’s time is left and when it has passed, who they mention and why one may come late.
Reference
- How deadlines are counted
How Dueline counts each deadline, and every report GDPR, NIS2, DORA and CRA ask for: what starts its clock, how long it gives and DORA’s weekend rule.
- What is stored
The permissions Dueline asks for, what it reads and as whom, what it stores in Forge storage and for how long, and why nothing leaves your Atlassian site.