Clearlane
EN
Quality and compliance apps

Validation support

Regulated teams must validate the software they use for quality records. This page gives you what a supplier should provide: how each requirement is addressed, what stays your responsibility, and ready-to-run test scripts.

Runs on Atlassian Your data stays in your Atlassian site.

Last updated 4 November 2026

Clearlane apps are designed to help you meet the requirements below. They are not certified, and no software can be “compliant” on its own: compliance comes from the validated system together with your procedures.

On this page: 21 CFR Part 11 · Controlled Documents · ISO 13485 · CAPA · Training records · Read & Understood · IEC 62304 · Tests · Cyber Resilience Act · CRA · Supplier assessment

Download the test scripts

Each OQ script carries a document number, a version and a date, names the app version it covers, and gives the requirement each test addresses. Installation and performance qualification stay your responsibility: the IQ and PQ templates help you record them.

Each script lists the objective, the steps, the expected result and space for the result, the tester and the date. Run it on a test space or project, attach screenshots, and keep it with your validation file.

How new versions reach you

For CAPA, Controlled Documents, Read & Understood, Tests, Risk Register, CRA and Breach & Incident Reporting, new versions are grouped: at most one production release every two weeks, on a Tuesday, starting on 17 November 2026. A release is made outside this rhythm only for a security fix, a data loss or corruption fix, a serious problem that may block a customer, or a feature that is indispensable to show a customer or prospect and was requested in writing; its release notes then say why. A major version (new permission or outside connection) waits until your site administrator approves it in Atlassian. Clearlane publishes OQ scripts for Controlled Documents, Read & Understood, CAPA, Tests and CRA; for Risk Register and Breach & Incident Reporting, a line that mentions OQ steps refers to your own test steps.

The release notes of each version end with a validation impact line: “Validation impact: none” or the OQ section to re-run. We give at least 30 days’ notice before any functional change that affects signed records, signatures or approval workflows. Atlassian Cloud apps cannot be frozen per customer: every customer gets the same version. Every production version and its validation impact line: validation change log.

What the supplier provides

  • The apps run on Atlassian Forge (Runs on Atlassian): no Clearlane servers, nothing leaves your Atlassian site.
  • Every release is tested with automated tests of the full workflow before it is published.
  • Release notes on the Atlassian Marketplace, and a security policy with a way to report vulnerabilities (security).
  • Supplier assessment, filled in (PDF): company, hosting, security, release process, support and validation materials on two pages. The same answers are in our trust center.

21 CFR Part 11 · Controlled Documents

RequirementHow the app helpsYour responsibility
11.10(a) ValidationSupplier testing of every release (automated tests of the full workflow). OQ test scripts on this page.Validate for your intended use (IQ/OQ/PQ), keep the validation file.
11.10(b) Accurate and complete copiesEvidence file as PDF; register export as CSV; Confluence page export includes the control block.Define how copies are provided to inspectors.
11.10(c) Protection of recordsRecords kept in Atlassian’s storage for your site; page history kept by Confluence.Retention and backup of your Atlassian site. Export evidence files before uninstalling the app.
11.10(d) Limiting accessAtlassian login and Confluence permissions; optional edit lock during approval.Manage accounts and permissions.
11.10(e) Audit trailTime-stamped audit trail of lifecycle, signature and read events, visible to space administrators.Review it as your procedures require.
11.10(f) Operational checksEnforced sequence: Draft, In review, Effective, Obsolete.—
11.10(g) Authority checksOnly the named approvers can sign; settings reserved to administrators.Name the right people.
11.10(i), (j) Training and accountabilityRead-and-understood records per revision support training records.Training, written signature policy.
11.50 Signature manifestationName, date and time, and meaning shown with each signature and in the evidence file.—
11.70 Signature and record linkingSHA-256 fingerprint of the signed content: an edit during review cancels the signatures; an edit after approval is flagged “Edited since approval”, and the approved revision keeps its fingerprint.—
11.100 General requirementsSignatures tied to unique Atlassian accounts.Verify identities; send the certification to FDA.
11.200 Signature componentsTwo components: Atlassian login plus a personal signing password asked at each signature.—
11.300 Password controlsSigning passwords stored hashed (scrypt); blocking after repeated failures.Password policy, periodic review, loss procedure.

Electronic signatures in detail: what is recorded, how it is protected, and the limit to know →

CAPA signs plan approvals and closures with the same signature engine (signing password, fingerprint, blocking).

ISO 13485 · 8.5.2 Corrective action · CAPA

RequirementHow the app helpsYour responsibility
8.5.2 a) Review nonconformities, including complaintsAny Jira work item can become a CAPA: complaint, audit finding, defect, incident. Problem step with source and severity.Define which events open a CAPA and how complaints are reviewed.
8.5.2 b) Determine the causesGuided root cause (5 whys, cause categories) with a guard against “human error” and “training” as causes; similar CAPAs shown.Investigate and decide the root cause; the app guides, it does not decide.
8.5.2 c) Evaluate the need for actionSeverity, containment and a documented decision before the plan.Decide whether action is needed, proportionate to the effects of the nonconformity.
8.5.2 d) Plan, document and implement the actionSigned action plan; actions as linked Jira work items with owners and due dates.Approve the plan and make sure the actions are carried out.
8.5.2 e) Verify the action does not adversely affect requirements or safety and performanceEffectiveness criterion and verification recorded per action; your assessment is written in the plan.Assess and document the effect on requirements, safety and performance.
8.5.2 f) Review the effectivenessDated effectiveness check with reminder; “not effective” returns to root cause; signed closure.Judge whether the actions were effective and decide on closure.
Records (4.2.5, and ISO 9001 10.2.2)Evidence file as PDF with every step, signature, attachment and audit event. Nothing is deleted.Set retention periods and archive the evidence files.

Since 2 February 2026, the FDA Quality Management System Regulation (QMSR) incorporates ISO 13485:2016 by reference.

Training records and 21 CFR Part 11 · Read & Understood

Read confirmations bound to each page version, optional comprehension questions and an optional signing password.

RequirementHow the app helpsYour responsibility
ISO 13485:2016 6.2 e) Records of trainingPer person, page and version: confirmation date and time, tries and signature, in the Readers tab, the Evidence PDF and CSV exports.Define which documents require training, and keep other evidence the app does not cover (practical training, skills, experience).
ISO 13485:2016 6.2 b), e) Training after document changesA new page version asks everyone to confirm again; earlier confirmations stay on record by version.Decide when a change is minor and give a clear reason when keeping confirmations.
ISO 9001:2015 7.2 c) Evaluating the effectiveness of the actions takenOptional questions check understanding before confirmation; the People view shows per person what is confirmed, pending or late.Questions show understanding of a page, not competence: assess competence with your own methods.
ISO 9001:2015 7.2 d) Retaining the evidenceEach person can export their own record (“Export my record”); space admins export the People view and the audit trail.Retain these exports according to your records procedure.
RequirementHow the app helpsYour responsibility
11.10(a) Ability to discern invalid or altered recordsEach confirmation is bound to the page version and to a SHA-256 fingerprint of its title and content. A confirmation sent for a version that changed meanwhile is refused.Validate the app for your intended use (for example with the test script on this page) and keep the evidence.
11.10(b) Accurate and complete copiesThe Evidence PDF and the CSV exports give readable copies of confirmations, previous versions and the audit trail; the PDF loads the whole trail.Decide which export is your official record and archive it.
11.10(c) Protection of recordsData stays in Atlassian storage. Stopping a request, a new version or kept confirmations never delete earlier confirmations or history. Names of closed Atlassian accounts are anonymised by the app; their confirmations stay.Set your retention period and archive exports, also before deleting pages or uninstalling.
11.10(d) Limiting system accessAccess follows Confluence accounts and permissions; a space can limit requests to space admins. Named lists, questions and the Evidence PDF are limited to the request owner, the requester and space admins.Manage accounts, groups and page and space permissions; remove leavers promptly.
11.10(e) Audit trailTime-stamped entries with the person for requests, confirmations, failed questions, new versions, kept confirmations, closing, reopening, reminders and setting changes; signing password resets are listed, with date and author, on the app’s global settings page. The app has no function to edit or delete them.Review the trail regularly. Setting changes are logged without old and new values and repeated actions within an hour are grouped: keep your own record of settings.
11.10(f) Operational checks (sequencing)A confirmation is recorded only after all questions are answered right and, if required, the signing password is given. Keeping confirmations requires a reason.Decide which pages need questions or signatures and set the spaces accordingly.
11.10(g) Authority checksEach action is checked on the server against the person’s Confluence rights (page edit, space admin, owner or requester). Signing policy and password resets need a Confluence admin.Give space admin and Confluence admin rights only to authorized people.
11.50 Signature manifestationA signed confirmation records the name, date and time (UTC) and the signed statement; the Evidence PDF shows them with the signature ID.Check that the fixed statement (“I confirm that I have read and understood this version of the page…”) matches the meaning your procedures require. The name shown is the Atlassian display name, anonymised when the account is closed: keep the Evidence PDF as the signed record.
11.70 Signature/record linkingEach signature belongs to one confirmation of one page version and fingerprint. When confirmations are kept after a minor change, the signature is not copied to the new version.Control page editing and use “Keep confirmations” only for truly minor changes.
11.100 Uniqueness of electronic signaturesEach signature is tied to one Atlassian account and to a signing password that only its owner sets.Never share or reassign accounts, verify identities, and send the certification letter to FDA (11.100(c)).
11.200(a) Two identification componentsSigning uses the Atlassian session plus a personal signing password, asked at every signature.Enforce strong Atlassian sign-in (SSO, two-step verification, session timeouts).
11.300 Controls for passwordsMinimum length configurable from 8 to 64 characters, lock after 3–10 failed attempts for 5–1,440 minutes (defaults 8, 5, 15), salted scrypt hash, admin reset, each reset listed with its date and author for site admins.Set the policy, define password ageing (the app has none) and follow up repeated lockouts (the app sends no security alert).

IEC 62304 · 21 CFR Part 11 · Tests

Test cases, campaigns and requirements coverage in Jira, with signed runs and closures. Traceability: the Coverage tab and its CSV export list each requirement with its test cases and their results; the campaign PDF report has a requirement coverage section.

RequirementHow the app helpsYour responsibility
IEC 62304 5.5.5 – software unit verification (results documented)Unit verification done manually can be written as test cases and executed in campaigns: result per step, comments, who and when, signed if required.Automated unit test results cannot be imported: keep them in your build system and decide which unit verification is recorded here.
IEC 62304 5.6 – software integration and integration testing (tests, regression, records, problem resolution)Integration test cases with steps and expected results are run in campaigns; each run records the result, the bugs found, the tester, the date and the case version executed.Define the integration strategy, regression scope and acceptance criteria; record test configurations and tools (for example in the campaign description).
IEC 62304 5.7.1 – establish tests for software requirementsTest cases hold actions, test data and expected results and are linked to requirement work items; the coverage view lists requirements with no test case.Write the requirements and the tests, set the pass/fail criteria and make sure every requirement is covered.
IEC 62304 5.7.2 – use the software problem resolution processA failed step becomes a Jira bug in one click, with steps to reproduce, expected and actual result, linked to the requirement; the bug’s panel shows the run that found it.Handle these bugs in your problem resolution process (triage, criticality, fix, closure).
IEC 62304 5.7.3 – retest after changesEvery case version is kept and each run records the version it executed; a run can be restarted on the latest version, a closed campaign reopened with a recorded reason, or a new campaign created.Decide which tests to repeat, modify or add after each change, including regression tests and risk management activities.
IEC 62304 5.7.4 – evaluate software system testingCampaign counts, pass rate, the coverage view (passed, failed, blocked, not run, not covered) and the PDF report give the data for the evaluation.Evaluate the adequacy of the tests and whether results meet the pass/fail criteria, and record that evaluation (for example with the signed closure).
IEC 62304 5.7.5 – software system test record contentsEach run keeps the steps and expected results executed, pass/fail per step with comments and bugs, the case version, the campaign’s Jira version, the date and the person who executed it; the PDF report gathers them.Make sure the campaign version names the build tested, and record test configurations and tools, which have no dedicated field.
Traceability between software requirements and tests (IEC 62304)Test cases link to requirement work items; the coverage view and its CSV export list each requirement with its test cases and their results, and Jira search can filter on testCoverage.Keep the links current and keep the exports or reports you need as records.
IEC 62304 7.3 – verification of risk control measuresIf risk control measures are Jira work items, test cases can cover them and the coverage view shows their verification status.Identify the measures and keep the hazard-to-measure traceability outside the app; judge whether the verification is sufficient.
IEC 62304 5.8.1 and 5.8.2 – verification complete before release, known residual anomaliesA closed, signed campaign and its PDF report show which runs passed, failed or were not run and which bugs were found.Decide the release, and evaluate and document the residual anomalies.
IEC 62304 9.1 – prepare problem reportsThe bug created from a failed step names the campaign, the case and its version, the steps to reproduce, the expected and the actual result.Add type, scope and criticality, and run the rest of the problem resolution process in Jira.
IEC 62304 9.8 – test documentation contents (testing after a change)Retests after a fix are recorded as runs with results, bugs, version tested, date and tester.Link the fix to its retest and record test configurations and tools.
21 CFR 11.10(e) – audit trailThe app writes a time-stamped history (who, what, when) of cases and campaigns: creation, every case version in full, requirement links, run status changes, every change of a recorded step result or note with its previous value, results cleared by a restart, bugs, files, signatures, voided signatures, closure and reopening with reason; it cannot be edited in the app and is printed in the PDF.Judge whether this history suffices for your records, and keep the PDF reports for the retention period.
21 CFR 11.50 – signature manifestationsEach signature shows the signer’s name, the date and time, and its meaning as a statement (execution of a run, or approval and closure of a campaign), on screen and in the PDF.The name is the Jira display name, refreshed by the app and erased for closed accounts: keep the PDF report as the signed record.
21 CFR 11.70 – signature/record linkingA signature holds a SHA-256 fingerprint of the signed content, checked again on every display and in the PDF; any later change removes the signature and records it as voided.Include this check in your own validation of the app.
21 CFR 11.200 – electronic signature components and controlsEach signature needs the Atlassian sign-in plus a separate signing password, asked at every signature; only the person who recorded a result can sign it.Ensure unique, personal accounts, verify identities before granting them, and send FDA the letter required by 11.100(c).
21 CFR 11.300 – controls for identification codes and passwordsMinimum password length (8 to 64, default 8) and lock-out after 3 to 10 failed attempts (default 5) for 5 to 1,440 minutes (default 15); passwords are stored as scrypt hashes and nobody, administrators included, can see them.The app does not enforce password ageing and sends no alert on lock-outs; a forgotten password is reset by a Jira administrator (recorded in the history of changes): set procedures for these.

Cyber Resilience Act · CRA

Clearlane CRA helps with the requirements below; it does not submit anything to ENISA’s single reporting platform. Reporting obligations under Article 14 apply from 11 September 2026.

RequirementHow the app helpsYour responsibility
Article 14(1)–(2): actively exploited vulnerabilities — early warning within 24 h, vulnerability notification within 72 h of becoming aware, final report no later than 14 days after a corrective or mitigating measure is available (reporting applies from 11 September 2026).Once the security team qualifies a case as actively exploited (signed), the app computes the three deadlines from the awareness time and the fix availability date, shows them in local time and UTC, and prepares each report’s fields with ENISA’s labels, ready to copy. Each submission is recorded with its time, reference, the text sent, who recorded it and whether it was on time; a report with an empty required field cannot be recorded.Decide whether a vulnerability is actively exploited and when you became aware of it. Submit each report yourself on ENISA’s single reporting platform (the app does not submit anything) and record the submission in the app.
Article 14(3)–(4): severe incidents having an impact on the security of the product — early warning within 24 h, incident notification within 72 h, final report within one month after the incident notification (reporting applies from 11 September 2026).Incident cases record whether the incident is severe and whether unlawful or malicious acts are suspected; the app computes 24 h and 72 h from awareness and the final report one calendar month after the recorded notification, and proposes the report fields.Assess whether the incident is severe (Article 14(5)), submit each report on the single reporting platform yourself, and record each submission.
Article 14(8): inform the impacted users (and, where appropriate, all users) of the vulnerability or incident and of the mitigating and corrective measures they can take.For a reportable case, closure stays blocked until “Users informed” is recorded (when, channel, text); the app proposes a notice built from the case, the fix and the security contact. The CSAF advisory gives the same information in a machine-readable format.Send the information to impacted users through your own channels and check that the text is accurate and complete.
Article 13(8): support period reflecting the expected time of use, at least five years unless the product is expected to be in use for less.Each version records its market date and support end; five years are proposed by default, a reason is required for anything shorter, versions whose support ends within 6 months are flagged, and the end of support is carried into the ENISA fields.Determine and make known the support period of each product, and handle its vulnerabilities and provide security updates throughout that period.
Annex I Part II(1): identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.Imports one SBOM per product version (CycloneDX 1.x, SPDX 2.x or 3.0, JSON), keeps the file’s SHA-256, marks direct dependencies when the file states them, searches every SBOM for a component and version range, and exports a CycloneDX 1.5 file.Produce complete and accurate SBOMs with your build tools and import a new one for each version placed on the market.
Annex I Part II(2): address and remediate vulnerabilities without delay, including by providing security updates.Each case gets a fix target date proposed from its severity, late fixes are flagged in the register and in the owner’s reminder e-mail, and the security update or mitigation is recorded with its availability date.Develop, test and distribute the security updates, and set target dates that match your own risk assessment.
Annex I Part II(4): once a security update is available, share and publicly disclose information about fixed vulnerabilities (description, affected products, impact, severity, remediation); publication may be delayed in duly justified cases.Builds a human-readable advisory and a CSAF 2.0 file from the case, records each published revision with the file’s SHA-256 and attaches the file to the work item; a delay can be recorded with its reason.Publish the advisory where users can find it, and decide whether a delay is duly justified.
Annex I Part II(6): facilitate the sharing of information about potential vulnerabilities, including by providing a contact address for reporting them.The security contact set in the settings is written into every advisory, CSAF file (publisher contact details) and user notice, and reports received as Jira work items can be opened as cases.Operate and monitor the contact address, publish it, and route incoming reports into Jira.

What stays with you

  • Validation for your intended use, and revalidation when you change your use or after a new app release that matters to you.
  • Procedures (SOPs), training, and the written policy that makes electronic signatures binding.
  • Account management, permissions, retention and backup of your Atlassian site.

Questions from your quality team or auditor: [email protected].