When does the "Next Era of Jira" begin?

[Justin Vander Ziel]

According to an announcement made in 2024, Atlassian is/was "combining Jira Software with Jira Work Management to create a tool for all teams called… well, Jira " However, this documentation page still describes how to tell the difference between the two. 

• Are/will/have the two products being/be/been merged or do I have to choose one or the other?
• We have a group of engineers, a software developer and cloud engineers working together - what's the best product for us?

[Chris Rogers · Accepted solution]

Hi @Justin Vander Ziel 

The products have been merged and are effectively just referred to as "Jira".

As for the documentation you linked, it's more about the different project types available in Jira, largely as a result of the merge.

If you have software developers and engineers, Jira is the best product for you, as it gives you the options of both types of projects.  If you're more interested in the Service Management side of things (Incidents, Service Requests, Change Enablement, etc), Jira Service Management would be the product you'd want.

[Trudy Claspill]

Adding to this, phrasing differently...

Prior to the "merge" you could license:

• Jira Work Management - and get just Business type projects
  -OR-
• Jira Software - and get Software AND Business type projects

After the merge you license just one product now called "Jira" and get both Software and Business type projects.

The merge eliminated Jira Work Management as a separately licensed product.

As part of the merge Atlassian has kept the two distinct project types; Software and Business, each having some distinct functionality. But some of the functionality of each has been made available in the other, like the Summary page previously only available in Business projects is not also part of Software projects.

So the choice you make is not between Products, but rather between the type of projects you want to use.

Software project templates offer you pre-built setups related to "software" development with the Scrum or Kanban methodologies, providing you with standard work items types, workflows, and agile board layout and reports.

Business project templates offer pre-built setups that don't include Scrum and Kanban support. The target audience was business process teams that didn't need the added layers of agile methodologies

[Jack Brickey]

Back to how it used to be. Yay!