Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I have a question about installing expired licenses for Jira.

Seonghwa Hong August 1, 2021

Hello everyone,

My customer has been using Jira Software (Server). The end date of their license is Feb 22, 2016.

By the way, they applied the license when they moved the server, and the following message was confirmed:

clipboardImage.jpeg

 

Jira 7.1.9 have been released on July 6, 2016. The last version released before the end date of Feb 22, 2016 is version 7.1.0. So they installed version 7.1.0. But, they can see same message.

It can be installed normally, but when they restart Jira, got the above message.

When I checked the log, I found the following:

The following JIRA Agile upgrade tasks have been run on this system

        JAG UpgradeTask  46 started at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354)
        JAG UpgradeTask  46 ended   at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354) and took 5 ms
        JAG UpgradeTask  47 started at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354)
        JAG UpgradeTask  47 ended   at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354) and took 18 ms
        JAG UpgradeTask  48 started at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354)
        JAG UpgradeTask  48 ended   at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354) and took 2 ms
        JAG UpgradeTask  49 started at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354)
        JAG UpgradeTask  49 ended   at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354) and took 159 ms
        JAG UpgradeTask  50 started at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354)
        JAG UpgradeTask  50 ended   at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354) and took 378 ms
        JAG UpgradeTask  51 started at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354)
        JAG UpgradeTask  51 ended   at 07 Mar 2017 10:52 within JAG v7.1.23-DAILY20160627065553 (5c85b488779c8354) and took 2 ms

Is it because Jira is automatically upgraded to version 7.1.23? If anyone knows this problem, please let me know what to do.

Thanks.

 

Regards,
Seonghwa Hong

1 answer

0 votes
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 3, 2021

Hi @Seonghwa Hong ,

Do you know what version of Jira they were on before trying to upgrade? I ask because Jira 7.0 has a critical upgrade task - for example, upgrading directly from Jira 6.4 to Jira 7.1 would cause problems.

Along with that, if you'd be willing to post the SEN number (not the whole license, just the SEN-xxxxxxx), I can verify the expiration date of the license.

Finally, is your customer considering an upgrade to Jira Cloud? If so, we can get them sorted out with a license to at least get upgraded to Jira 7.6, the minimum version required to use the Jira Cloud Migration Assistant app.

Thanks,
Daniel | Atlassian Support

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, atlassian community, loom ai, atlassian loom ai, loom, atlassian ai, record recaps of meetings, meeting recaps, loom recaps, share meeting recaps,

Loom’s guide to great meetings 📹

Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.

Register today!
AUG Leaders

Atlassian Community Events