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

EOL JIRA Server - JSM licensing question for upgrade to Data Center

StephanieC

This article ( https://confluence.atlassian.com/adminjiraserver/migrate-from-server-to-data-center-993929572.html ) notes that to upgrade to Data Center from Server, the apps on the licenses must match, but we are deprecating the use of JSM and uninstalling it just prior to the Data Center Upgrade (from Server)

What are the appropriate steps to mitigate having to purchase a JSM license when we will not be using it? We plan to uninstall and delete all JSM artifacts prior to the Data Center Upgrade as we were not using the key differentiated functionality (KBAs, SLAs, etc) and our VOC showed that our agents & users prefer making & managing all tickets in JIRA Software to using the portal.

Will we need to go to https://my.atlassian.com/ and do something before getting the trial Data Center license for our DEV instance?

I will need precise instructions for our Project Manager for the project plan and CIO who does the licensing renewals/purchasing.

Accepted answers

Nic Brough -Adaptavist-

Basically, don't do anything.

If you are migrating from Jira Software + JSM to a Jira Software system only, just don't buy the licences for JSM.

In your case, the best thing you could do is to talk to the people using JSM projects now, and gradually swap them all over to JS projects, so that when you do the migration, there's no JSM left to worry about.

All comments

Nic Brough -Adaptavist-

Basically, don't do anything.

If you are migrating from Jira Software + JSM to a Jira Software system only, just don't buy the licences for JSM.

Radek Dostál

Also, probably obvious, but you may want to remove the license key from JSM, unless JSM is straight up uninstalled - Jira doesn't like when it has 2 different license types for application (server and dc), it's somewhat confused and can give errors either when trying to apply the DC license (it might not allow you to), or it might cause errors with plugin licenses (claiming the license type does not match).

Nic Brough -Adaptavist-

Yes, some upgrade processes may fall over if you don't have a valid JSM licence while it is still installed. It's very good advice to blank the server key out before you migrate to DC.

Apps do not fail on upgrade or migration, they just stop doing anything until you apply the licences matching the new system type.

StephanieC

Awesome - thanks ! That is exactly our MIgration plan - build out replacement projects & artifacts for Service projects and migrate BEFORE upgrading to Data Center.

Ill keep this link on our migration plan page as a reminder :-)

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server