Handling licenses when switching to another JIRA instance

Hi there; we've got the following situation:

We currently have JIRA 5.2.11 running on one server (25-user license, support expired), and the most recent JIRA, including JIRA Agile, on another (evaluation licenses). We plan to make the latter productive soon, and keep the former as an archive.

This is what I assume needs to be done:

  1. Buy a JIRA Agile license for the new server.
  2. Use the existing JIRA license on the old one (since, to my understanding, one license can be used for multiple instances as long as there's only one production instance).
  3. Change the JIRA license on the old server to the corresponding "developer license".

Is that about right, or is there anything I fundamentally misunderstood? If so, what needs to be done instead?

Thanks in advance.

2 answers

Yeah, that sounds right. Remember that your JIRA Agile license has to match your JIRA license. In your case, a 25-user license.

Actually, it turns out we both overlooked something - the new version we're using was released after our support expired, and that meant we had to renew the license (an additional $600). Makes sense in hindsight, but I didn't anticipate that.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,717 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you