Our team is in charge of administrating Jira Server for our organization. To safely upgrade Jira with minimal impact, we created a test instance (version 7.13.1) that is using a developer license. We want to switch the commercial license from our current production instance (which is on an older version of JIRA -- 6.4.12) over to it, making our test instance the new production instance. This is the rough plan: * Shut down the production instance * Update the License key of the test instance to the commercial license * Turn on the former production instance (we might want to view the old data in it for archival purposes) * Update the License key of the former production instance to use the developer license Is this possible? Will we be able to switch to a license being used by a Jira instance if it's offline? The same questions apply to our Confluence Server instance. Thanks!

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; } } }

Switching from Developer to Commercial License for Jira

Iñigo Ambas

Our team is in charge of administrating Jira Server for our organization. To safely upgrade Jira with minimal impact, we created a test instance (version 7.13.1) that is using a developer license. We want to switch the commercial license from our current production instance (which is on an older version of JIRA -- 6.4.12) over to it, making our test instance the new production instance.

This is the rough plan:

Shut down the production instance
Update the License key of the test instance to the commercial license
Turn on the former production instance (we might want to view the old data in it for archival purposes)
Update the License key of the former production instance to use the developer license

Is this possible? Will we be able to switch to a license being used by a Jira instance if it's offline? The same questions apply to our Confluence Server instance. Thanks!

Accepted answers

Nic Brough -Adaptavist-

Mostly that list is fine, but I would not bother stopping Production. Just paste in the developer key, so it becomes a dev/test system (Although you should also do something about warning your people that it is becoming a test system!). Pasting the key in the UI is a LOT easier than trying to mess around with file and database systems on a shut-down system.

All comments

Nic Brough -Adaptavist-

Iñigo Ambas

I see, so it is possible for two instances to be using the same developer key? My main concern was that I would be prevented from entering a key that's already in use by another instance.

Nic Brough -Adaptavist-

It is, yes, Atlassian expect larger setups to have dev, test, DR etc, and that's what the key is for.

Iñigo Ambas

Thank you for clarifying!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

jira

jira-server