Guides
Plain answers to the questions Jira and Confluence teams ask every week.
Free tools and templates
- Jira automation steps calculatorSteps and cost of each rule, your allowance and what to change, from your rules export.
- CRA Article 14 deadline calculatorThe 24-hour, 72-hour and final report deadlines, in your time zone.
- CRA support period calculatorThe end date to announce and how long updates stay available.
- Monte Carlo forecast calculatorA likely and a safe delivery date from your weekly throughput.
- IEC 62304 software safety classThree questions give class A, B or C, with the reasoning to keep.
- NIS2 incident reporting deadline calculatorEarly warning, notification and final report deadlines of Article 23.
- CRA vulnerability handling policy templateAnnex I, Part II turned into a one-page policy for Confluence.
- CAPA report templateCause, actions and effectiveness check, in the order auditors read them.
- SOP template for ConfluenceVersion, approval, review date and training at the top of the page.
- Software test plan templateBuilt around one question: which requirements were tested, and with what result?
- Project budget templateBudget, cost so far and where you will land.
- Confluence page review checklistFive questions per page and a review rhythm for your space.
- Read and understood record templateWho read which version, and when, on one page.
- Internal FAQ template for ConfluenceGive each recurring question one home, with an owner.
- Delivery forecast update templateA likely date, a safe date and one decision, every week.
- Project plan template for JiraDates, owners and dependencies, ready for a Gantt chart.
- Weekly flow review templateStuck work, flow numbers and one change, in 20 minutes.
- Risk register templateRatings before and after treatment, criteria set in advance, reviews dated.
Guides
- Jira sprint burndown not working? Six checksFlat line, sudden jumps, points only: what Jira is really counting.
- Use case: prove who read which procedureFor quality managers, with Read & Understood.
- Use case: report an exploited vulnerability in 24 hoursFor product security leads, with CRA.
- Use case: which requirements were tested?For software V&V leads, with Tests.
- NIS2 early warning: the first 24 hoursWhat makes an incident significant, and what to send first.
- Test traceability matrix in JiraRequirements, tests and results that stay true, IEC 62304 included.
- Internal Q&A in ConfluenceStop answering the same question twice.
- CRA timeline: the Cyber Resilience Act datesReporting since September 2026, everything else in December 2027.
- CRA or NIS2: which incident reporting applies?Who reports what, where and when, and when both apply.
- CRA SBOM requirementsFormat, scope, one SBOM per version, searchable in 24 hours.
- CRA support periodAt least five years, the end date to show, what to record.
- Leaving Atlassian Data Center with regulated recordsThe dates, five checks per app, and how to keep old records usable.
- Report an actively exploited vulnerability from JiraThe CRA early warning, notification and final report, step by step.
- How to choose a Jira or Confluence appTen questions to ask before you install, for any app.
- CRA vulnerability reporting in JiraThe three Article 14 deadlines, from your work items.
- Read and understood in ConfluenceWho read which version of a procedure, and when.
- Document control in ConfluenceApprovals, signatures and read confirmations an auditor can follow.
- How to manage CAPA in JiraThe six steps auditors expect, without heavy setup.
- How to track project budgets in JiraFrom worklogs to cost, margin and the expected final cost.
- How to forecast a release date in JiraGet a date range with odds from the data Jira already holds.
- Monte Carlo forecasting in Jira, explained simplyA worked example, and the mistakes to avoid.
- How to make a Gantt chart in JiraFrom Start and Due dates to a plan you can read at a glance.
- How to find stuck work in JiraCompare what is running with your team’s usual pace.
- How to find outdated pages in ConfluenceA monthly routine that keeps a space trustworthy.