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
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
Hello dear Jira users,
I'm Rathesh, a Jira Software Product Manager. I want to take a minute of your time to talk you through two features that have been highly requested for the basic roadmap view, and bring value to your team by allowing you to plan and track work at a deeper level.
Note: These features are new to the basic roadmap view which appears next to the board and backlog available on all editions of Jira Software cloud. Learn more about enabling the roadmap.
Advanced roadmap users on Jira Software cloud already have the ability to schedule child issues & view releases on the roadmap.
The first new functionality we are currently rolling out (Look out for it the next 2 weeks) is the ability to visualize and schedule tasks and stories for kanban teams from your roadmap view, as shown below:
This added functionality allows you to include both your epics and underlying stories in a single view when working with kanban teams. With this addition, you can more accurately predict and communicate project progress and deadlines. And if a due date of a child issue moves, the roadmap automatically updates your parent-issues' schedule bar, meaning that your plan is always up to date. Note: the epic dates will not automatically update if the epic already has specified start/due dates set. This ensures that the team is aware of child issue movements on an epic that has been planned toward a specific date.
This feature is not enabled by default, but it’s easy to turn on (if you have project permissions). Learn how to enable child-level planning for kanban teams.
This also unlocks many of the other features that we’ve released in the past six months on the roadmap view for kanban planners. You can use the dependencies tool to indicate which issues are reliant on each other to identify risks and potential pitfalls in your timeline. Learn the ins and outs of child-level issue planning for kanban teams.
If your project settings have "Start date" and "Due date" fields to be visible for child-issue types, the dates scheduled on the roadmap will also appear in the board and backlog. Treat them as time estimates for the purpose of prioritizing work and getting ahead of blockers. They can and should be updated as plans change.
The second major feature that we’ve shipped this month is the ability to show releases on your roadmap.
In the image above, each dot in the row labeled Releases represents a release, and their colors tell you their status. This extra information helps you identify potential conflicts between your team’s work and the target release dates. Armed with this information, you can better plan work against release dates, make adjustments to deadlines or scope, and communicate progress to stakeholders. Learn more about what you can do with releases on your roadmap.
Adding releases to your roadmap is simple, as well: the toggle to turn them on is in the View settings menu on your roadmap. Learn more about showing or hiding releases on your roadmap.
These features might seem simple, but a lot of work has gone into them to get a balanced, yet simple solution for the roadmap– not just from development teams on our side, but also from this wonderful community we have here.
I’d like to take the opportunity to thank all of the members here who participated in the EAP or the Beta testing of these features, as well as those who have given feedback or voted on feature requests. Without the help of this group, this feature wouldn’t have been as robust and valuable.
If you have any questions or concerns, feel free to drop a comment to get the conversation rolling.