What's new in Jira 7.0?
Having been involved with Atlassian since JIRA 1.0, I've seen it change dramatically over the years. Its become essential software in most Enterprises and industry sectors. Today, Atlassian launches JIRA 7.0, revealing a completely new approach and a new suite of products in the JIRA family.
With over 50,000 customers worldwide, I rarely come across people at conferences who don't know what JIRA is. Even Jessica Alba uses JIRA!
It's no surprise that the latest version of JIRA is set to have a significant impact in Atlassian Ecosystem. In this blog we have an early look at the main changes.
What's new in JIRA 7.0?
The biggest change that all JIRA users will notice first is that there are now 3 editions of JIRA. Each one comes with its own defaults around workflows, statuses and custom fields that make sense for the sorts of teams that would be using each edition. Of course, JIRA is still totally adaptable and customisable to each organisations specific needs.
- JIRA Core is a stripped back and simple JIRA system which is blank out of the box
- JIRA Software a JIRA system built with software development in mind, with a set of complementary plugins like JIRA Agile preinstalled
- JIRA Service Desk a JIRA system built with service desks in mind
How does the new model work?
Adaptavist are known as the Most Technically Excellent Atlassian Expert and for those who are technically inclined, there's a few key things to understand about what this release means.
Atlassian have created a new plugin module for applications and JIRA has been split into core code and plugin bundles which describe each application. The first two of these applications are Software and Service Desk. This separation enables JIRA Core to become better and more powerful as a platform and also presents an opportunity for further applications to be developed.
Licensing has changed a bit too. The JIRA Software license now enables both JIRA itself as well as JIRA Agile (which previously needed its own license key). We'll be looking at licensing in more depth in a forthcoming blog post.
What does this mean?
I believe this will result in simpler and better articulated license structures, as well as better articulated offerings for clearly-defined markets. It will make it easier for teams to adopt JIRA and for organisations to buy into Atlassian. It will also help Atlassian to develop JIRA as a platform as much as they support it for specific use cases.
Do you agree? Comment below and let us know what you think or if you have any specific questions about JIRA 7.0.
