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

Plugin licensing conflict with JSM trial.

gheorghe_Ciorba

Hello guys ,
I am currently facing an issue with our Jira Data Center plugin licensing.
The situation is the following: we recently renewed our Jira Software licenses and our plugin licenses. At the same time, we also have a trial license enabled for Jira Service Desk, because we are planning to migrate the service desk to another platform.
The problem is that, once the trial was enabled, Jira appears to report an unlimited number of licenses. As a result, when we try to apply the renewed plugin licenses, the plugins detect the maximum user tier as unlimited. Because of this, each plugin becomes unusable and requests an upgrade to match the maximum number of licenses currently detected by Jira.
My question is the following: if we temporarily apply another Jira Service Desk trial or license with a specific user tier that matches the number of plugin licenses we purchased, so that we can successfully apply the plugin licenses, and then switch back to the current Jira Service Desk trial license, will the plugin licenses continue to work as intended? Or, after the next reindex or license check, will the plugins detect the unlimited trial tier again and become invalid?
Would this be the best approach in this situation, or is there a better way to handle this type of licensing issue so that we can apply and use our plugin licenses properly?

Thank you.

Accepted answers

Arkadiusz Wroblewski

Hello @gheorghe_Ciorba

I would not do that.

This does not look like a reindex problem. It looks like a licensing conflict. If the JSM trial is what pushes the instance into the higher tier, switching back will most likely cause the same issue again.

If this is Jira Data Center, the license types on that instance also need to stay aligned, so mixing license models is not a good path.
The safer options are remove the JSM trial from production, test this on a separate non-production instance and raise it with Atlassian or the app vendor and ask for the supported licensing path for your setup.