(Obsolete) Supporting Server Clients

Naming convention

The examples below uses “Release Management App“. The same approach applies to “Release Gadgets App“.

Latest from Atlassian on “Server End-of-Support“

  • On February 15th, 2024, Atlassian will officially end support for Jira Server related products. This means that Atlassian will no longer provide assistance with purchasing, renewing, upgrading, or any form of support whatsoever for any Server Apps for Jira, Confluence, Bitbucket, Bamboo, and Crowd.

  • Sametime, Atlassian informed Partners it will continue to offer extended support to certain customers until February 15, 2025 in scope incentives programs published in late Q3 / early Q4, 2023. If you are part of it you are probably on track with Atlassian to finalize migration at your pace.

  • Therefore, Atlassian has decided to keep the server apps and hosting selector with the server option (with limited tabs) until at least February 15, 2025. This decision has been made to ensure that customers, particularly those under extended support, can receive assistance by accessing the marketplace and obtaining the required information.

If you are not part of Atlassian incentive plan for migration and you need more time beyond February 15th, 2024 to finalize the migration at your own pace the following section will provide details how we can support you meanwhile.

What if you need more time?

We (Release Management & Gadgets) are sharing the same code base between our Server and Data Center Apps so they look, function and behave absolutely the same on Jira Server and Data Center platforms.

Earlier this year we also realised that Data Center licences issued for our Apps are well suit for Jira Server and a number of clients leveraged this option to continue their trials on Jira Server and purchase a license for DC App to use on Jira Server.

How to stay licensed?

So, we are happy to offer you an option to stay licenced with Atlassian for our products and use it on Jira Server for the time needed to make decision / finalize migration.

Below is a step by step guide to do it:

Since you are purchasing via Atlassian you can always refund it following standard Atlassian refund and cancelation policies. Read more here: https://www.atlassian.com/licensing/purchase-licensing#payments-refunds.

As a result of the purchase you will be a license key for our DC App product.

Now let’s apply it to your Jira Server:

  • Go to Settings \ Applications

  • Click Manage Aps \ Manage Apps

  • scroll to “Release Management for Jira“ and expand

  • click Edit License key and Copy exiting one somewhere to restore later in case of issues

  • Enter the new one purchased

  • That’s it - you got Release Management App DC License applied to your Jira Server.

Any issues please do not hesitate to reach out to our support to help.

Migration to Data Center?

If you decide to migrate to DC later 2024 you are now well set from Release Management perspective, namely:

  • use Atlassian Migration assistant to copy your data from Jira Server to Data Center

  • kick off Release Management trial for your Jira Data Center

  • re-create boards you need and assure everything is working

  • take the instructions above to apply DC App license key you purchased

  • renew/upgrade it when time comes as usual process.

Any issues please do not hesitate to reach out to our support to help.

Migration to Cloud?

If you decide to migrate to Cloud later 2024 we encourage you to explore our Migration to Cloud guidance.

Money wise we won’t double charge you and we will give you discount on our Cloud App pro-rata to remaining DC App licence. Opt in for promo code via our support team.