Software development teams building medical devices or SaMD commonly run two separate systems: Jira for sprint planning, issue tracking, and defect management, and a QMS for quality events, CAPAs, change control, and regulatory records. Each system does what it was built for well. The compliance problem is the gap between them.
IEC 62304 requires a software lifecycle that covers planning, requirements, architecture, detailed design, implementation, testing, maintenance, and configuration management. Anomaly handling under IEC 62304 Clause 9 means that a defect identified in testing must be evaluated, resolved, and documented in a way that is traceable to the software release and risk file. A defect closed in Jira without a parallel record in the QMS may not appear in the CAPA history, the software problem report log, or the technical file that a notified body reviews.
Linking the two systems typically works in both directions. A Jira issue flagged as a potential regulatory concern can open a quality event in the QMS. A change request approved in the QMS can generate a Jira task for the engineering team to implement. The result is a traceable chain: from the original anomaly report through the impact assessment, CAPA or change control decision, software change, verification testing, and updated technical file, without requiring someone to manually copy data between systems.
The whitepaper below covers how qmsWrapper connects with Jira for medical device software teams.
