Clearlane
EN
Clearlane CAPA · Jira

Corrective actions in Jira, closed with proof.

Containment, root cause, a signed action plan, actions as Jira work items and a dated effectiveness check, on the work items your team already uses.

  • ISO 9001:2026 §10.2
  • ISO 13485 §8.5.2–8.5.3
  • 21 CFR 820 (QMSR)

Designed to help teams meet their CAPA requirements. Your own validation still applies.

Play the demo1:07 · subtitled
Freefor up to 10 users
Runs on Atlassianyour data stays in your Atlassian site
No configurationno issue types, workflows or fields to set up
English · Français · Deutschfollows each person’s language
01

Root causes that go past “human error”.

Guided five whys and cause categories. When the answer reads like “human error” or “training”, the app asks you to look once more at what the process allowed.

  • Five whys, guided
  • Method, machine, material, people, measurement, environment, design
  • A prompt to dig one level deeper
Root cause step with five whys and cause categories
02

Similar problems, before they come back.

While you analyse the root cause, CAPAs on the same product or process, or with the same kind of cause, are listed so you can check whether similar nonconformities exist or could occur.

Similar CAPAs listed during the root cause analysis
03

Signed, and bound to the content.

A coordinator approves the plan and closes the CAPA with an electronic signature: name, date and time (UTC), meaning, a statement shown before signing, a personal signing password and a SHA-256 fingerprint of what was signed.

  • Change the problem, cause or plan, and the approval is withdrawn
  • The owner cannot approve their own CAPA, unless you allow it
An action plan approved with an electronic signature
04

Actions live in Jira.

Each action becomes a Jira work item linked to the CAPA, and its status comes back on its own. The CAPA then waits for its check date and reminds the owner. Not effective? It goes back to the root cause, and the failed check stays on record.

Corrective and preventive actions as Jira work items
Register and evidence file

Every CAPA, its status and its proof.

One register for the whole site, and a PDF evidence file per CAPA with every step, the actions, the signatures, the work item’s attachments and the audit trail: time-stamped, and no one can edit or delete it in the app.

01

Open, late, due

Plans to approve, checks due, median age.

02

Effective first time

The share of CAPAs that worked the first time.

03

Filters and CSV

For Excel, in English or French format.

04

Searchable in Jira

capaStage, capaDue, capaOverdue and more, in JQL.

The CAPA register showing two late CAPAs

Clearlane CAPA helps teams meet the CAPA requirements of ISO 9001 §10.2 (2015 and 2026 editions), ISO 13485 §8.5.2–8.5.3 and 21 CFR 820 (QMSR). Your own validation still applies.

How it works

From any work item, in six steps on one screen.

  1. Open the CAPA panelof a complaint, an audit finding, a defect or an incident. It is prefilled.
  2. Contain, analyse, planContainment, root cause and an action plan with a measurable effectiveness criterion.
  3. Sign, act, checkA coordinator signs the plan, actions run in Jira, effectiveness is checked on a set date.
Jira Service Management

From a customer complaint to a CAPA.

CAPA also works on Jira Service Management requests. When a customer complaint arrives through your service portal, open a CAPA straight from the request.

Works with Rovo

Ask Rovo which CAPAs are overdue.

Clearlane CAPA adds a Rovo agent, “Clearlane CAPA”. Ask it which CAPAs are overdue, what is waiting for you, where a CAPA stands or what its root cause was. It answers from the app’s own records, only with what you are allowed to see, and it only reads: it never changes anything. It works where Rovo is turned on for your Atlassian site; Clearlane adds no AI model of its own.

Permissions and data

The app runs on Atlassian Forge (Runs on Atlassian). You see a CAPA only if you can see its work item. Work items for new CAPAs and their actions are created with the permissions of the person who asks.

CAPA records, the audit trail, settings, Atlassian account IDs and the names shown at signing are kept in Atlassian’s storage for your site; signing passwords only as a salted hash. Reminders reach each owner as at most one e-mail a day, sent by Jira; nothing is posted on the work items. Nothing is sent to our servers or to anyone else.

FAQ

Questions, answered.

Where do I find it?
In Jira’s apps menu for the register, and in the CAPA panel of any work item.
Who can approve and close?
Coordinators: the people and groups a Jira administrator names in the settings, usually the quality team. Jira administrators are always coordinators.
Do I need to change my Jira setup?
No. Any work item can become a CAPA. There are no issue types, workflows or fields to set up.
Does it work in French?
Yes. The app follows each person’s Jira language, in English, French or German, in light and dark themes.
Is it available on Atlassian Isolated Cloud?
Yes. The app is listed on the Atlassian Marketplace for Isolated Cloud. It runs on Atlassian Forge there too, with the same permissions, and its data stays in Atlassian’s storage for your site.
Does it work with Rovo?
Yes. Its Rovo agent answers questions such as “Which CAPAs are overdue?” from the app’s own records. It only reads, and only shows what you are allowed to see.
Same family

Clearlane for Quality

Clearlane for Quality: controlled documents, read confirmations, corrective actions, test evidence and a risk register in Jira and Confluence — signed, traceable and kept in Atlassian.

Built and supported by Maxime Ragionieri, founder of Clearlane. Who’s behind Clearlane →

Free for up to 10 users.

Larger teams pay per user, billed by Atlassian on the Marketplace. No setup, nothing to install outside your Atlassian site. See the price for your team size →