<img height="1" width="1" style="display: none" src="https://www.facebook.com/tr?id=976470819114134&amp;ev=PageView&amp;noscript=1">

Top 3 Reasons to Be Excited Following the 2016 Atlassian Summit

If you’ve paid any attention to news surrounding Atlassian in recent weeks, then you knew already that this year’s Atlassian Summit – held in San Jose, California – was going to be something special and Atlassian’s team of developers, specialists, and business experts did not disappoint.

With so much buzz and speculation surrounding what Atlassian’s next steps were going to be, it was nice to be able to get some concrete information from the guys themselves with many of the details being of major interest for all attendees.


So, without further ado, here are our top three reasons GLiNTECH were excited, following the Atlassian Summit 2016.

1. Data Center as Default Option

One of the key talking points from San Jose was the announcement that Atlassian will be focussing on the Data Center license as the default licensing option for mid and large-scale proprietors with over 500 users each.

On the surface, the changes are relatively straightforward: Atlassian operators with over 500 users will be directed towards the Data Center version of the particular platform when they shop for a new licence, while smaller-scale organisations requiring less than 500 software users on a licence will still be able to order a non-Data Center licence.

However, digging a little deeper sheds some light on what Atlassian are trying to achieve with this change. Atlassian is aiming to position their Data Center versions at the forefront of what larger scale users require, enabling them to offer the functionality and support to users at this level. And this is relevant to deployers of all Atlassian’s products: the Data Center version will become the default option for larger scale customers.

This underlines Atlassian’s strategic commitment to enhancing the Data Center version of each platform, and shows us that Atlassian is preparing to take this format to the next level. At the conference, it was revealed that organisations utilising Data Center versions of Atlassian products will have access to enterprise-specific features on an exclusive basis, and that more of these features would be developed over time.

In addition to this, the major Atlassian announcement is that Data Center-version products would feature native support for Amazon Web Service – AWS – Amazon’s cloud computing platform. This is part of a collaborative effort between AWS and Atlassian, which will feature quick-start templates jointly developed by the two organisations.

2. New and Improved Home Page Function in Confluence

Closing out the keynote 'Innovation in Team Collaboration' session at this year’s summit was Sharif from Atlassian’s platform team. He focussed on outlining how Atlassian’s developers are committed to providing a seamless multi-platform experience for users of the software. As the vast majority of us utilise multiple pieces of Atlassian software together within our organisations, this is a particularly exciting area of progress from the company.

Sharif explained that much of the development process for Atlassian tools is built upon direct customer feedback. This feedback showed that software users tend to behave similarly across each tool they are working with; something which Atlassian strive to be able to support effectively. To demonstrate one of the ways in which Atlassian aim to achieve this, Sharif unveiled the new personalised home platform, enabling entire teams to keep track of the work they are doing and to build seamless integrations between Atlassian products. Sharif explained that – initially – the home platform will be compatible only with JIRA and Confluence, but will expand over time to cover the whole Atlassian family.

Once the platform is launched, it will be accessible from the header bar within each open tool, simply by clicking the ‘Home’ icon in the top left-hand corner. This will bring up a unified home screen through which users can: view, access and manage their ongoing tasks, see all their recent activities and pages, view the work of other team members, easily search across both JIRA and Confluence platforms for user and administrative tasks, facilitating smart collaborative effort over a range of different products.

All users will be able to launch new projects with just the touch of a few buttons, while administrators will be able to carry out a range of administrative tasks within the new hub. It promises to make the experience more intuitive than ever for Atlassian customers.

3. StatusPage Integration with JSD and HipChat

One of the key points raised at the summit related to how Atlassian deals with an external problem; namely the influx of duplicate tickets created by users. Service Desk by itself fails to prompt users of website or platform issues as they arise, and so that Atlassian team recently bought StatusPage to help businesses better manage customer interaction more efficiently. 

Scott Klein – one of StatusPage’s co-founders – explained how this recent addition to the Atlassian family provides the missing communicative link between the different Atlassian products, harnessing the power of integration with other Atlassian applications like Jira Service Desk and HipChat to better meet this need.

Scott began by discussing downtime – specifically, how we respond to downtime – and how this is key to maintaining a high-level of service. He explained that communication is the only way to effectively respond to downtime: communication between different departments, between team members, and between your organisation and your customers.

StatusPage enables customers to quickly view and understand the status of projects within the system, to receive updates via whichever channel they prefer and used as a form of internal communications as well. The vast amounts of working hours associated with answering inbound service queries are reduced, team efficiency and productivity is raised, and customer happiness is secured; all by clueing your customers in on the status of their service or project.

From the back-end, Atlassian users can utilise the cross-platform integration discussed earlier to view StatusPage updates via another Atlassian product, for example, Jira Service Desk. This interactivity will be rolled out across the full Atlassian family in time, but to begin with, both JSD and HipChat are compatible with StatusPage.

Which of these updates are you most excited about? Don’t forget to let us know.