I am setting up my first Advanced Roadmap via Plans. I have added two projects as issue sources and then assigned those sources for the teams I am including in this view. Each of those teams works in 2-week sprints. We don't manual add start and due dates, so my goal here is to populate the dates based on sprint start/end dates. I have noticed though, that it's not working (as shown on the screenshot below).
However, if I change the issue source to board, not project, then the timeline information is populated.
Could someone clarify whether this is the correct behaviour? Meaning when I use projects as issue sources, I won't get the start/due date auto-populated based on my sprints?
Thank you!
welcome to the Atlassian Community!
Have you tried the following?
The fields Start date and Due date will not use the connected sprint's start date and end date (unless you would copy those values via smart values in automation)
Hi Dave! Thanks for a quick reply. Since the goal here is to track work across teams which work in their respective sprints, grouping by sprint doesn't make sense for us.
Initially, when I had projects chosen as the issue sources, I have also set "Inferred dates" to "Sprint dates" in the "Scheduling" tab. My assumption was that this is the exact setting that would allow me to pull in start/due dates based on the sprint dates. What am I missing here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bumping this. This feature does not appear to be working as intended, unless I am misinterpreting the instructions. The epic shows a timeline block; all issues that have end dates show a timeline block. Otherwise, all issues within the epic do not show anything on the timeline, even if they are part of an active sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ignore the above! If you're having this problem, check the issue source. If you use a "team" it doesn't know what sprint to look at -- use a "board" as the issue source instead.
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.