ISO Atlassian Blog

On February 15, 2024, Atlassian will discontinue technical support for its server products. This means that Atlassian customers will have to decide whether to migrate their existing server instances to the cloud or to the Data Center Edition or whether to continue working with the risk of a post-end-of-support server. In this blog post, we compare the benefits of an Atlassian migration with the risk of a post-end-of-support server. The aim is to help you, as an Atlassian customer, make an informed decision in good time.

Atlassian Unleash, a one-day event on the topics of "Agile" and "DevOps", took place at the Berlin Congress Center on February 9. In the keynote speech, the Australian software company Atlassian presented new features for the existing product suite. The keynote motto "Level up to Mulitplayer Mode" already clearly indicated where the journey is heading: teams should be able to work together even better and more playfully in Jira, Confluence and co.

Atlassian has announced that it will change the offering structure of its server products on February 15, 2023. These changes are related to Atlassian's focus on cloud development and thus mark the end of the lifecycle of the server variant.

Everyone is talking about migrating to the cloud. The focus is usually on the technical aspects of the move and on streamlining existing data and mapping previous processes 1:1 or in an improved form in the cloud. However, the unloved stepchild of these projects is testing. But how do you test the Atlassian Cloud?

What points do you need to check off before migrating to the cloud? Before you lift your IT infrastructure into the virtual clouds, do a preflight check with us!

On October 16, 2024, price and package changes for various Atlassian products will take effect. These changes affect the prices for the cloud versions of Jira, Confluence, Jira Service Management, Opsgenie, Bitbucket, Atlassian Guard (formerly Atlassian Access) and Compass.

Jira schemas are a complex and sometimes difficult to understand area of responsibility. And not only for new Jira administrators, but also for Atlassian veterans. It is not uncommon for a Jira admin to have to laboriously work their way through many different schemas when a customization is required. With larger and historically grown systems, there can even be hundreds of schemas.

Until now, the issue of data residency was a knock-out criterion for many European companies when it came to the Atlassian Cloud. Only customers of the Enterprise license were free to choose whether their data should be stored in the EU, the USA or worldwide. Users of the Standard and Premium licenses, on the other hand, had no choice.

Atlassian has recognized that this is a blocker for many (potential) customers and is now relenting: From 01.07.2021, you can create new cloud instances in any realm (EU, USA or worldwide) at no extra cost, regardless of whether you are a Standard, Premium or Enterprise customer.

Atlassian Data Residency: Does this apply to all data?