I'm confused about the comments related to SPRINTS and BACKLOG.
Are you saying "Sprints" and "Backlog" functionality IS GOING AWAY ALL TOGETHER? In other words, are you removing our ability to run sprints and hold issues in backlog from ALL project types?
I hope NOT. This is CRITICAL to our work. Removing it would mean the downfall of Jira.
Atlassian Team members are employees working across the company in a wide variety of roles.
November 14, 2024 edited
@Mark B Wager - thanks for reaching out for clarification!
Sprints and backlogs will remain in software projects as they always have been, though the potential addition of sprints and backlogs to business projects is being evaluated for the future.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Regarding this merging of JWM into Jira, please see the question below where someone asked Atlassian Support about the impact on automation usage limits.
Spoiler: it appears usage maximums are reduced (again), eliminating the counts JWM provided.
I have a similar question to Douglas Brian. Our site is primarily used as FLS tool for our clients. We just recently completed our migration from Jira Server to Jira Work Management Cloud.
I am one of the technical admins for the system and am curious how the migration will impact all of the customization that we have implemented on the instance. Couple of questions:
How will the migration impact our current configuration?
What is the cost difference for migration from JWM to Jira?
Is there downtime expected during the migration?
If you can help with answering the questions above, I would like to arrange a call and chat about what the impact will be.
Atlassian Team members are employees working across the company in a wide variety of roles.
January 24, 2025 edited
@Anastasia Tarutina - The migration will not disrupt projects or usage. Pricing will align with Jira plans after the migration is complete, and Jira Work Management customers are offered a 10% discount on Jira subscriptions. For more information, please refer to the FAQs. If you have any additional questions, feel free to contact support. Thank you!
Atlassian Team members are employees working across the company in a wide variety of roles.
February 9, 2025 edited
@Loren Smith - Approvals is still under consideration to be added for software projects. We don't have an update on timing at the moment, but will share this feedback with the product team!
Thanks everyone for this rich discussion — I’ve been closely following the Jira Work Management (JWM) to Jira Software transition as part of my organization's migration strategy.
To help others in the same boat, here’s a quick summary and solution based on what’s confirmed so far:
Approvals in Jira Software Projects: Currently under consideration. This has been a key blocker for audit-heavy workflows (e.g., SOX compliance). My recommendation: use native Forms in JSW for now and supplement with Marketplace apps like “ProForma” until native approvals are rolled out. Keep track of Atlassian Roadmaps for updates.
Board Visibility for Done Issues: For team-managed projects, there's no direct board setting like in company-managed ones, but “Custom Filters” now offer a decent workaround. You can create a filter to exclude Done issues after X days and apply it across multiple views.
Cost & Licensing Impact: The 10% discount for 12 months after migration is helpful, but organizations with split user bases (JWM vs JSW) should prepare for unified licensing. Consider running an internal cost-benefit audit using Atlassian’s pricing calculator and adjust app tier plans accordingly.
Sprint/Backlog Functionality in JWM: Not available yet in business projects post-merge, but given user demand, it’s likely being prioritized. Meanwhile, if you need backlog/sprint features, I suggest transitioning high-agility business teams to JSW projects and using issue type schemes + workflow sharing to reduce complexity.
Would love to collaborate further with anyone facing similar transition concerns — feel free to tag me!
58 comments