Just Jira - Jira Work Management's merger back into Jira Software

[Martin Cleaver]

Adding list and calendar views for the purpose of building Software - excellent. As is Plans and Goals for all teams. But I'm left puzzled by the folding of Jira Work Management into "just Jira".

I'm perplexed by this as there's a lot of software build stuff that's in currently in Jira Software that won't be used by teams with lightweight "Work Management" task needs. Also, the lack of segmentation feels like Atlassian is retreating from the "Every Team" space.

I've been looking through the videos from Team 24 - is there a talk on the reasoning for this decision?

Cheers, Martin.

[John Funk]

Hi Martin - Welcome to the Atlassian Community!

There was a lot of confusion around licensing and the segregation of tools. True you won't need to use software build stuff with your business teams, but that's why there are still two different types or projects - Software and Business. But it didn't make sense to say tools like the List screen, Forms, Calendar, etc. should only be available for business teams and not software teams. 

It's actually a step back to what it used to be in my opinion. What's your biggest objection to the merger? 

[Robert Wen_Cprime_]

Hi @Martin Cleaver ! Welcome to the Atlassian Community!

As a consultant for an Atlassian Gold Partner, I can tell you it's a bit easier talking about a "Jira for multiple kinds of teams and projects" instead of a sprawl of Jira tools (Service Management, Product Discovery, Align, etc).

I look at it the way it's presented in both Cloud and Data Center.  You can have business projects that start from specific project management templates that will pull from what was developed for Jira Work Management/Jira Core and the Software projects will add capabilities from Jira Software on top of that.