You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are planning to move to the Atlassian cloud solution. One question I have is currently we can manage the releases of updates as is required within our change management framework. For context we have to document any changes to our environment to be FDA approved.
When we move to the cloud solution we recognise that updates will be pushed out to us instead of us pushing the updates.
My question is really, how can we still manage updates and releases to fit in with our compliance requirements?
Hi @Ellis McMahon ,
For more control over updates and releases, Premium cloud plans currently offer a feature called "Release tracks" which allow you to review, test, and bundle your updates 2 weeks ahead of time (vs. continuous releases).
However, I did a bit of digging and found this advice from another community member:
You can make a SaaS application part of your FDA regulated suite of applications, but you will require certain documentation such as contingency plans, local backup, and acceptance from a company compliance officer.
It's my recommendation to consult with a company that specializes in FDA medical/pharmaceutical regulation in order to determine what is required.
It sounds like to meet your compliance needs, you may just need to clearly document and employ contingency plans, including Atlassian cloud backups. I also found this article from 2017 which might be helpful.