Key Facts about Confluence & Jira as QMS Software
Yes, you could set up a QMS in this software, but you'd have to take care of electronic signatures and document versioning yourself.
Yes, the software contains a ticket-like functionality to manage requirements, but you'd have to set up a compliant structure yourself.
Yes, you can try this software out for free!
No, you can't export your data in a structured way and are probably locked in.
Yes, this software has its own text editor, that means you can create and edit documents directly in the software.
Yes, this software has a cloud-hosted option.
No, this software does not have a self-hosted option.
Billed per user, $7.75 - $15.25 / user / month
$305 / month (20 users)
No, this company is losing money.
For whatever reason, Confluence and Jira still seem to be popular choices among software companies. Why? I’m not so sure. Maybe it’s the same reasoning as for why startups think building microservices is a good idea: Because huge companies like Google do it, it must be a great idea, right? Right?
Wrong. Confluence and Jira are reasonably terrible (but not the worst) choices as QMS software.
I’ve written about them before, so I’ll just refer you to my other posts here, check it out: How to set up a QMS in Confluence and Jira?.
I’ve also written about companies trying to integrate Jira into their QMS. Many companies, believe it or not, use Jira and ask themselves the question: “Can we somehow integrate Jira tickets into our eQMS software?”. The short answer is that that’s a terrible idea, but for a longer answer, check out my article on Jira integrations.