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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are a small enterprise with 80 employees/Jira users working in a regulated environment (medical device development regulated by FDA). Regulations require us to validate process software and configurations before it is used in a productive setting. We were able to address all requirements by using the on-premise server version of Jira, so that we can control the time point a new version is rolled out and also can take care of e.g. the data retention requirements. Now Atlassian forces us to switch in a - for us - ridiculous short time frame to either Data Center or Cloud.
Data Center would result due to our size in a crazy cost increase by approx. factor 10x, but we would be probably able to address all requirements - at least if we are willing to pay the full price until the retention time (usually 10 years) of the last project using Jira has ended. So at least 0.5 million USD for a period where probably nobody is actually working with the system and data.
Cloud would be slightly more expensive than today, but I don't see how we can fulfill our regulatory requirements if we cannot control when and how often new features are rolled out by Atlassian. Data retention is probably ok as long as Atlassian keeps up operations of Jira Cloud. However, also during the 10 year phase out the system probably continuously needs maintenance resources, because of frequent changes triggered by Atlassian. Instead, we could freeze an on-premise server during the phase-out and just fire it up if it is required, e.g. for audits.
I would be interested to hear from users working in regulated domains (medical, aerospace, pharma, ...) how they use in Jira Cloud or Jira Data Center and what their experience is regarding aligning regulatory requirements with the Atlassian products and operations.
Has the time Atlassian products can be used in regulated environments ended (at least for small and medium enterprises)?
We are in a very similar position. We are a small pharmaceutical company of about 65 employees and have been using Confluence and Jira for almost 10 years to manage many of our GMP processes. We are able to do this in this highly regulated space as we are using the server version of these Atlassian products and we can control the updates. A move to Cloud is not possible as it would put us in a continuous revalidation cycle and becoming impossible to remain in compliance. A move to Data Center would be preferable, but the minimum user count of 500 users makes it cost prohibitive. I am hopeful that Atlassian can provide Data Center at a lower user count (100 users). As it stand, this announcement has significant impact to our needs. I would love to hear feedback from anyone else in this or similar regulated spaces and know your path forward.
Same situation on our side. We are a small medical IT device producer with 95 employees. We introduced Jira/Confluence a few months before Atlassian announced end of support for our server-based system.
Our architecture in Jira is based on Jira Insight to connect company assets and digital twins with procedures/documents. Smart Attachments and goEdit apps are in use to control “file-based” approvals. Structure for Jira is our powerful issue-browser to support multi project management and inter-department projects/workflows.
In Confluence we are using Document Management for Confluence to provide ISO 13485 QM documentation and technical documentation for our products.
In addition to former posts in this thread we are faced with two more critical problems:
We are now looking for a way to continue using the server installation after Atlassian support has been discontinued. This is not a long-term perspective, but we need much more time to find a solution for these massive problems.