As the Schedule child issues by dates feature has been fully released, I believe this ticket can be closed, but I will wait a week before doing so in case any watchers disagree. Thanks!

Hi Jira team 
I was hoping to use the roadmaps functionality to visually represent the work across the team. We set start and end dates on all our stories but found out that the dates for stories are represented by the Sprint dates. This isn't very helpful at all, and almost always means the Epic will be flagged as ending prior to the stories underneath it.  Having the dates on stories aligned to start and end dates will be a massive improvement on this functionality and will save me using other tools to do the job. 

Thanks

Chris 

Hi all, thanks for your detailed feedback on this ticket so far. We are now considering this request of being able to sequence/see dependencies within a sprint. We will keep you updated on this ticket. 

If you would like to discuss this in more detail or have alternative use cases, please feel free to book in 30mins to chat with me: https://calendly.com/ratheshr/planning-convo 

Cheers,

Rathesh Richards - Product Manager, Jira Software

Hi Jira Team,

we just tried to use roadmaps with child issues and after having set start and due dates we realised that dates are always aligned to the sprint dates.
As for many of our colleagues we find this approach very limitating and, in our organisation this means that we have to use some other tools to visually represents timelines and dependencies. Dependencies, within the same sprint, are the more needed functionality to enable.
As more persons are involved in a single sprint, the need for them to focus and understand task dependencies is fundamental.
What we suggest is to give to each team the opportunity to choose if using issues start-due dates or sprint start-due dates.
Thanks for listening

Hey b20502c4bd67 ,

just wanted to say a HUGE thank you for providing this valuable, elaborate, well-thought through and balanced feedback. That's phenomenal and very insightful. Thank you for putting so much thought and time into it and explaining the why behind that ask so clearly. Our team will definitely take your points into considerations when working on further iterations and the future direction of this feature.

Thanks again for your input, really appreciated.
Kind regards,
Albert Kavelar | Jira Software Cloud, Roadmaps Team

Hi Jira Software Team,

1. First congratulations on the Roadmap view - the UX of scheduling epics is very smooth!

2. I'd like to highlight this is a highly differentiating feature. My team (small startup, team of 6 engineers) went though multiple issue tracking tools.

• We first started with Notion, which has a a superb Timeline feature that we were using both for planning and on a daily basis to track progress during standups. However, we hit some other limitations and decided to switch.
• We then adopted Github Issues / Projects after it was released in Beta and seemed full of promises. Github was at the time making a huge emphasis on their own Timeline feature but never shipped. See this discussion for more details. After waiting for over a year and seeing very little momentum in improvements over the initial Beta state, we decided to switch again.
• We are now in the process of adopting Jira Software Cloud, and the Roadmap view was a major factor in our decision

3. Here's how we would like to use the Roadmap view and why this improvement (JSWCLOUD-23411) is super important for us:

• We use a Scrum project.
  • We went through the background in JSWCLOUD-18668, and understand that scheduling issues in the Roadmap view was possible with Kanban projects.
  • We balanced the pros and cons between Scrum and Kanban, and even though the ability to schedule issues was super important for us, we felt we were leaving too much on the table by going Kanban, as our workflow is deeply anchored in Sprint iterations. We were concerned about losing all the nice workflows around sprint start and end, capacity estimation, backlog/sprint view...
• "Micro-managing" sprints timelines makes sense for us
  • We have a huge emphasis on pace and speed, and being able to "timebox" issues even in the span of a week makes a lot of sense for us
  • We think having a clear, planned game plan at the onset of a sprint (in the form of a timeline with tentative start and end dates for each issues) has a tremendous effect on urgency and focus.
  • Correction: we don't think, we know it, because that's how we were operating when using Notion, so we know the positive effects of micro scheduling within a sprint
  • This means we would like to use the Roadmap view for the micro picture rather than the big picture
• We are using another tool (ProductBoard) to get a high-level picture of our roadmap

4. How we think it could take shape in Jira:

• We understand some (probably larger) teams may like to see children issues automatically aligned with a sprint timeline.
• But we think each team should have the choice!
• We think it would make sense for Jira to have a setting offering to enable child issues scheduling.
• This setting would align the behavior with Kanban projects when enabled.

Thank you!

Hi, just to share my teams experience here once again ( same comment as in issue JSWCLOUD-18668 )

"First of all thanks for working on this issue, daterange for child issues in kanban has unlocked a great visible overview for my teams progress. 
Now a question...
I understand that in scrum having child issues showing the same daterange as the Sprint they belong to makes sense according to the scrum framework, however it doesn't give any added value to Jira as a tool since it is self evident that child issues in scrum must be solved in the timframe of the sprint they belong to. 
My team and some others I've read would much rather have the same functionality as in the Kanban Roadmap where you can visually see the deadlines for each childissue to get a better visual overview of the workflow order of tasks and dependencies inside each sprint. maybe this is something you already consider?"