nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do you handle audit evidence and traceability when Jira is part of your regulated workflow?

Halina Cudakiewicz_Deviniti_

Hello,

I'm looking into how teams in regulated environments (medical devices, industrial, automotive, etc.) manage audit evidence and traceability when Jira is part of the toolchain. Not promoting anything, just trying to understand how this actually works day to day.

Things I'm curious about:

How audit evidence gets assembled today. Is it mostly manual at the end of a cycle, or is there something more continuous in place
How approvals, baselines, and execution history get captured and whether that lives inside Jira or somewhere else entirely
Where the process feels the most painful or time-consuming when an audit actually comes around

If you've found a workflow that keeps this manageable, I'd love to hear how you built it. Also happy to talk it through on a quick call if that's easier than typing it all out.