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 - Any thoughts on adding predecessor/successor functionality within Advanced Roadmaps? Predecessor/successor functionality should shift dates as stories are scheduled into sprints. I envision using this functionality at higher levels in the plan.
I found this work around however being able to add predecessors/successors is key to doing long term planning. I'd be fine with using blocks and blocked by if the dates moved. I'm managing a project with 10 different technical teams and need to understand when one teams dates shift how it impacts the entire project.
I assume by higher levels in the plan you mean epics and issues further up in the hierarchy?
If so, you may be better off clearing your start end end dates from those issues and have the dates roll up automatically in Advanced Roadmaps. In that case, they won't be saved tot the actual issues in Jira, but you can use and share the Advanced Roadmaps view to communicate the dates.
To do this, just remove the dates from your epics and higher level issues. I believe you can then set the roll up dates option in view settings of your plan. See this support article to learn more.
Hope this helps!
Thanks Walter but not exactly what I'm thinking. We roll up dates already. Its the epics, initiatives that have not been scheduled into sprints that are the issue.
Stories for Epic 1 are scheduled into sprints
Epic 2 is estimated to take 10 weeks (original estimate). No work has been scheduled and work will start after Epic 1 is complete.
I see, but I may be missing something. Epics and initiatives are not scheduled in sprints. The issues in those epics are. So as soon as you start schedule the issues in those epics, they will follow.
To manage the time dimension in your high level, longer term planning, using versions makes more sense. They have a start and end date which can be fixed or dynamic. By assigning epics (or even initiatives) to those versions, you can get an idea of where they may be expected on the roadmap, even if you have not even defined any sprints in the backlog yet. Those sprints are for fairly short term planning and execution of the actual work.
On an additional note, you can enable scenarios in your plan where you can use the auto-schedule option to simulate what may happen if certain work is delayed. It does, however, take a lot of things into account, and so I would recommend reading up on how it actually works