How does the license agreement work when upgrading JIRA/Confluence on a test server?

unknown

The documentation on upgrading JIRA strongly suggest that the upgrade should be performed in a test environment. Since the license key is derived from the Server ID it would obviously mean that a new key is needed for the test server.

Generating a new key is fairly easy, but I would like to know what the official answer is for this kind of procedure. How is the upgrade supposed to be performed with regards to license? The question applies to Confluence as well.

(And thinking of it: I there no limit on the amount of servers that can run JIRA from one license?)

Nic Brough -Adaptavist-

At the moment (Atlassian are looking at site license stuff, so this may change in the long run)

1. Your License entitles you to run one and only one production server (with up to X active users, depending on license). It's a breach of contract to run more than one production server on one license.

2. Your license entitles you to run as many dev/test servers as you think you need.

3. There are provisions for failover, but I'm fuzzy on those, not having needed to read them a lot (I know "cold standby with a developer license" is ok)

On point 2, go to your Atlassian account, find your current licence and look for the "developer license" - you can use that to do all your testing on separate systems, and even commission/upgrade your production server before re-applying your main licence.

Atlassian understand that this can be a pain, and are immensely flexible about this. If in doubt, talk to them, but frankly, it's your intent that matters more than the fine-print.