My company has a server version of JIRA for production because of security issues. What if we get (buy) a cloud version only for development/restructural and testing needs? Are they the same? I'm thinking of making changes to workflows, structures changes, etc. on cloud, then move my changes to our server JIRA version which is our production/life.
They are separate code bases these days I believe, so are separate products. Moving configuration changes from cloud to server is not likely to be easy, but do try
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Darya,
What you'll notice is the Cloud version is usually a version or two ahead of the Server version and includes features that may not be in Server yet, e.g. the Kanplan backlog did not make it into Server for at least 3 months after it was introduced to the Cloud version.
Here are a couple resources to help you determine the best course forward:
In addition, the functionality of some add-ons may be different, .e.g ScriptRunner is a bit different on Cloud than on Server.
If you do decide to move to Cloud please review the Migrating from JIRA Server to JIRA Cloud documentation before proceeding.
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Darya,
No worries. To add to what Matt said, the JIRA code is being developed as Cloud and Server independently so there may be some version mismatch issues and feature loss going from Server to Cloud as the Cloud development is a version or two ahead of Server.
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do not bet on functions in Cloud ever making it into Server, and vice-versa. The message at the last couple of summits was clearly what Brandon and Matt have said - they are different products with different audiences, and some features may never cross the gap.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic. I don't think we will go with this solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you're happy with server (because of your security questions), stick with it! There's no need for a migration unless there are significant benefits.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was just thinking of dev environment on cloud. My IT probably doesnt's want to use space for dev. But I don't like the idea of restructuring my processes on production.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cloud and Server are too different for that to be worth it. I'd use your developer licence to run a dev/test server of the same version as production
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.