You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
The timeline feature in Work Management projects is not as full-featured as the roadmap in software projects. For one, tasks do not roll-up to their parent epics. There does not seem to be a method to group tasks together using versions either. Compare:
I thought I was going to be clever and create a "master" project for a team where they could view nice roadmaps for their projects. Nope, roadmaps only work if the issues are in the current project only.
I'm guessing there is no other work-around.
It feels like JWM projects are a little half-baked. I already have users asking if they can just use the competing product that we migrated them away from.
Hi Brandon,
Jira Work Management is a very new product and is continuing being improved upon. The Timeline is a different tool than the Roadmap tool, but the Atlassian folks are continuing to upgrade it and make it better.
Yes, it's clear that it is a work in progress. It's a bit frustrating that even though we pay for the full Jira Software platform that we can't make use of some of those features. In fact, in a certain way, some things are harder for us because I'm not allowed to grant our users the ability to create JWM projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Considering that function didn't even exist until a couple of months ago, I don't believe there was a price increase that was charged for this functionality.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are missing the point entirely.
I, as an administrator for a Jira Software instance, have less control over how my users are able to utilize JWM templates compared to an admin of a JWM only instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're right - I don't understand that point at all. That was nowhere in your question - you are comparing apples with oranges between Jira Software projects and Jira Work Management projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One year later and stories still don't roll up to epics and there haven't been too many improvements to these. unfortunate as our marketing team of 90 wants to leverage but we may need to move them to an entirely different tool.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello John,
Is there any update on this? It is really a pitty that these functionalities are quite different between both setups.
One thing i wonder: why is the Roadmap functionality (JSW) not copied over to the JWM-"Timeline" functionality? (then this was immediately the same functionality as in JSW)
Another question: will, on one point in time, both the Roadmap (in JSW) and Timeline (in JWM) become (nearly) the same as functionality (so both become as transparent as possible between both setups JSW & JWM)?
From UX-standpoint, i presume that would be the best (so when people/teams/companies move from possibly JSW to JWM the "transfer" would be very "light" on change)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Yannic De Baets - Sorry, but I have no update or answers to any of your questions. Someone from Atlassian would have to provide those.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk nesting tasks and stories in Epics in JWM project's timeline should be a basic feature. I'm quite shocked honestly that this is not supported.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Once again, you should discuss that with someone from Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To be clear, the board filter only contained one project, the JWM project. It did not contain issues from the "master" project where the board resides.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.