Jira Work Management is now part of Jira

[#1]

What's happening?

We will be merging this Jira Work Management group into the Jira group by the end of October 2024. As of May 1, 2024, the Jira Software group is now the Jira group. You can follow all Jira updates in the new group here. 

Why are we doing this?

We’re combining Jira Software with Jira Work Management to create a tool for all teams called… well, Jira. This evolution of Jira offers a shared place for every team to align on goals and priorities, track and collaborate on work, and get the insights they need to build something incredible, together. Read more about what’s new here.

What do I need to do?

All links will be automatically redirected, but your followed groups will not carry over. Go to the Jira group and if you aren't already subscribed, click "Watch" in the sidebar to subscribe to articles or questions. You can also sign up here to be the first to find out about new and updated Atlassian University learning opportunities.

What does this mean for Jira Work Management subscriptions?

Jira Work Management users will continue to have access to Jira Work Management until their organization migrates to Jira in early 2025. For more details on this migration, see FAQs here. 

I have a question about this change

If you have any other questions, just leave them in the comments below!

[Ryan Bullock]

I am not seeing any information on how this affects users that have access to Work Management through JSM. Will they need Software licenses to continue using their Work Management projects after migration?

[Arkadiusz Baka]

What with Jira Software DC?

[Abby Stiris]

@Ryan Bullock thanks for your question! No new licenses needed, they will be able to continue using their Work Management projects through JSM.

[Abby Stiris]

@Arkadiusz Baka there are no changes coming to Jira Software Data Center

[venkat patchigolla]

Hope after few years they won't end up in separate products again :)

[Violaine Iglesias]

Hello, I don't understand what is supposed to happen for the frontend views of Jira Work Management. We use it through a subscription to Jira Software (most team members actually use both Jira Work Management and Jira Software). We mostly use Jira Work Management for non-dev work because it's simpler to use and set up than Jira Software, but I'd be interested in an improved experience for the Jira Work Management projects - is that part of the change?

[Abby Stiris]

Hi @Violaine Iglesias there will be no major changes to Jira Work Management projects. I'd love to learn more about what you'd like to be improved. Can you share more about that? Also happy to jump on a call if you prefer!

[Violaine Iglesias]

Got it, thanks. With the addition of editable Lists to Jira Software, we might move our Work projects to it anyway, if we can find the time to migrate them without too much trouble. Lists/spreadsheets view were there main reason we use Work for non-dev work.

We use Jira Work Management as our CRM (mostly so we can keep everyone's tasks in the same place - we're a small company and our to-do lists sometimes span marketing, sales, product).

What I wish would be improved:

• Shared filters on views
• Shared workflows, issue and field types
• The ordering of statuses is wonky
• Moving an issue from one project to another

We love how easy it is to set up a new project, but feel like there are maybe too many limitations compared to Jira Software.

Happy to show you what we've done and maybe get some pointers.

[Douglas Bain]

I am responsible for a number of JIRA based products at my company. 

We do not develop a lot of software, so we have a small number of JIRA software (Premium) users. 

However, I have sold our organization on the use of JIRA Work Management and have been deploying it across our departments for the last 18 months. 

From what I have read, all of our JIRA Work Management users will need to be migrated to JIRA Software (Premium) users.   This will mean that on our next subscription, our licenses costs will increase by over 200%. 

In addition, the number of users will go over 100 meaning that all of our plugins will be charged at the 100 user banding. 

I would be interested in understanding how this particular change is beneficial for myself and our organization?   Did I make a mistake when I decided to roll out JIRA Work Management across our company?   or, should I  take a 200% increase in license costs as fair?

[Emilee]

Hi @Douglas Bain thanks for sharing your feedback and concern. I'll reach out to you directly so we can get a few more details to understand your license. 

[Kelechi Okoh]

Hello, I need help please.

Since the change, I noticed all our sprints and backlogs in a project merged into one table with filter.

How do we manage sprints and backlogs. Each time I try to use a direct link to our board, it displays "you are not allowed" and I am an org admin. Please advise.

[Anyi Weng]

Hi @Kelechi Okoh - Thanks for reaching out! There were no changes to sprints and backlogs. If you can send a note to our support team we'll help you get this resolved.

[Trudy Claspill]

Hello @Leslie Hubertus 

This announcement includes notification about the move of JWM Overviews to the Plans menu. With JWM Overviews moving to the Plans menu, does that mean that users now have to be members of the Plans User permission under Plans Global Permissions in order to create what was previously an Overview for JWM projects? Did a user previously require additional permissions to create a JWM Overview? I don't recall, but I think they did not. 

In an instance where both JWM and JSW production subscription exist and a user has been given only a JWM license, with the move of Overviews to Plans, do they now need a JSW license in order to create a Plan, to access the JWM Overview functionality they previously had while having only a JWM license?

There is a community Question where the OP says that since the move of Overviews to Plans, their users that have only JWM licenses are unable to create Plans. It is unclear if they have tried to add the users to the Plans User permission under Plans > Settings.

That makes it sound like having a JSW license and being added to the Plans Global Permissions might be required now to get the same functionality through Plans that was previously available with a JWM license and JWM Overviews.

[Oussema Marai]

hi @Abby Stiris  

[Oussema Marai]

@Abby Stiris  hi,

i used Jira and i loved Jira until you do this merge of Jira and Jira work management, i understand your objectives but your execution is so wrong :

1- any added user will be subscripted in the plan of Jira and Jira work management , so i pay 2 time for 1 new user because i need him to use the feature Plan. thats mean if i add 5 users now with 10$ for JWM and then add them to Jira with 12.48$ only to use the feature Plans i will charge 22.48$ ?! waw

2- the feature Plans is so ridiculous in terme of UIUX , really ! why did you change the JWM Overview's by this one !!! pls return it back pls you ruined the platform ! why did the subtasks and the tasks separated !! why when i click on a ticket a new tab opened !! 

PLS look the difference !!

for me as a project manager , now i can not follow up easily my all team with this new overview. 

i only chose this platform for my marketing company to 35 member just for  the Overview in JWM or i keep using Clickup or Monday !! 

really take my demands into consideration as a member and a client. for me if you can not keeping my all users using JWM even the new users i will cancel all my subscription. pls contact me in private its an urgent matter.

[Leslie Hubertus]

Hi @Trudy Claspill first off, thanks for engaging with this and helping promote visibility to @Oussema Marai's concerns as well. I've asked a SME to reply to both of you with more information, and believe the PM who worked on Plans will be responding soon. 

[Irene]

For visibility to others, @Trudy Claspill 's question was answered here: https://community.atlassian.com/t5/Premium-articles/Welcome-to-the-next-era-of-Jira-Premium/bc-p/2695397#M442 

[Irene]

@Oussema Marai , I have provided answers to your questions here instead, as it looks to be more comprehensive: https://community.atlassian.com/t5/Jira-Work-Management-Questions/Re-New-invited-user-in-premium-subs-can-not-create-an-ov/qaq-p/2698059/comment-id/11997#M11997  I have also emailed you directly to connect.

[Oussema Marai]

Thank you @Irene  and @Trudy Claspill 

[Kampaoh Tech]

@Emilee Same here. Jira Workspace is much better suitable for most of our non-IT teams, they even prefer Trello over JW. So they dont need all the bells and whistles that Jira Software, ie ithe Development section. On the other hand, the price increase kills us too. We understand the unification (Trello, Jira Workspace, Jira Software) but unless there is a better flexible UI which addapts to the non-IT and IT, it is going to be UIX problematic. 

This is not just about the huge impact in the budget, but also 3rd party plugins have a great impact here. If we are using 20 JW and 20 JS, tomorrow we will pay 40 Jira and 40 licenses to 3rd party plugins. Correct me if I am wrong.

TLTR: I believe Atlassian is still not there to merge both products since our members rejects the JS and prefers JW.

  

[Oussema Marai]

@Irene  Could we consider something else? I've seen this request so many times. I understand Jira has its special method and way to organize work, but we need this feature: the ability to assign two people to one ticket. Of course, time spent will be registered for both assignees. Each person will have their own ticket in their overview and their own notification, just to avoid the duplication of the same ticket many times. pls take this into consideration.

[Andrew Zimmerman]

I understand the unification at the product level, but can you please confirm that there will continue to be a distinction between software and business project types within Jira, or are project types going to be unified as well?

I ask because there is still feature variance between the two project types currently, and I want to be as clear as possible with end users selecting a project type for new project setups.

Thank you,
Andrew Z.

[Ravid]

Will the summery page be available for Jira as well?

[Anyi Weng]

@Andrew Zimmerman - Business and software projects will remain unique project types, but we plan to bring overlapping capabilities into alignment across the project types for a simpler UX.

@Ravid - The summary view will be coming as one of the areas of alignment across the project types.

Stay tuned for more updates as these changes happen!

[Loren Smith]

Will you be brining the approval functionality in workflows from the Business Projects to the Software Projects?

That is really the only thing (short of forms) that is holding us back from migrating our Business Projects to Software Projects...