Just an update for Enterprise accounts: 
The roll-out takes a little longer due to the communication required with our enterprise customers. For those customers part of an enterprise edition of Jira Software Cloud, if you have not seen it yet, this feature will be rolled out by September 15th (PST). 

Thanks Rathesh for linking those additional issues so we could vote for them!

ef95f667bfcb  thanks for the support! Go vote on issue 
JSWCLOUD-23411  to make our Jira dreams come true! 

Hi all, thank you for your continued feedback since the [release of the ability to schedule story-level issues feature |https://community.atlassian.com/t5/Jira-Software-articles/What-s-new-in-the-Roadmap-view-I-m-so-glad-you-asked/ba-p/2077594]for kanban projects.

We hear you. So, in order to dig deeper into the additional requests, understand the key problem, and how basic Roadmaps can help your team plan effectively - Here is an existing, and a new suggestion ticket that highlights the recent comments on this ticket:

• If you have the need for scrum teams/projects to be able to better sequence child issues within a sprint, feel free to highlight the problem with a comment and vote: 
  https://jira.atlassian.com/browse/JSWCLOUD-23411

• If your team feels they are missing some visibility of sub-tasks on the roadmap, then feel free to continue to vote here: 
  https://jira.atlassian.com/browse/JSWCLOUD-18677 

Thanks,

Rathesh Richards, Product Manager - Jira Software Cloud

Hi again Jira Team, 

also I was trying do use the same function (Daterange on roadmap from kanban project) while planning my company managed Jira project. There the function for viewing the datrange for childissues doesn't seem to be enabled :/ Since it's already on team managed level, it would make sense to have it on company managed project level aswell.

Thanks again! 

Does this extend to sub-tasks as well? Can it?

When will this feature be enabled for scrum board projects? I would love to be able to see actual end dates on child issues for issues that were completed before the sprint ended. 

1,000.000% Agree with Nora Buerhop's comment. It is abundantly apparent how long a Sprint is with current implementation; but for scrum, getting more fidelity in how long individual issues/tasks may take within a given Sprint is key and what, ultimately, provides valuable and necessary utility when trying to plan and manage large scale projects with thousands of issues/tasks. It makes no sense and adds zero value to visually show deadlines for individual issues/tasks by representing them as the same length of time as a sprint they are currently contained in. I'm sure there are many Jira users that don't follow an Agile/Scrum methodology to the the letter/by the book (gasp!) and often adapt it to work best for their needs and this should be considered where it can be on Atlassian's side. For example, I'm sure there are managers out there that may even create tasks that are (gasp!) longer than a determined Sprint interval and that may also be intended to span multiple Sprints along the way.

Thanks for listening!

 
9e85fad61184 added a comment - 10 hours ago
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?
 
Looking forward to your response! 

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?
 
Looking forward to your response! 

Hi aaf380f1e6a0 , sorry to hear that you're unable to schedule child issues: "I have the "Schedule Child Issue" switch set for both a Kanban and a Scrum project, and I cannot schedule any other Issue Types, aside from Epic, on the Roadmap." 

To further help you with this, can you please raise a support ticket ticket at https://support.atlassian.com/contact

Otherwise in the meantime, if the settings is turned on, can you please check the following:

• If sprints are enabled for the project ( i.e. you can see the sprints header on the Roadmap) then you can assign the child issues to sprints by clicking on the sprints dropzones. You will need some active/future sprints with start and end dates in your backlog. If you hover your mouse over the row, you should be able to see the dropzones appear (light blue bars). By clicking on the dropzone it will assign the child issue to a sprint, and you will see the bar. 
• If sprints aren't enabled for the project (i.e. you don't see the sprints header on the Roadmap) then you you can click/ click & drag the bar on the row to set the start/due date and make the bar appear for the child issue. Or otherwise, if you set a Start date and Due date for the child issue through the issue details panel on the right, it should appear. 

Hi all, 

Thank you for your patience throughout this time. As commented above - the ability to schedule story-level issues with dates is now available for Kanban projects on Jira Software Cloud on all editions, Free included. Our research with agile software teams using Kanban led us to this approach - so thank you for being involved in the EAP or Beta, and for your feedback here. 
More here: https://community.atlassian.com/t5/Jira-Software-articles/What-s-new-in-the-Roadmap-view-I-m-so-glad-you-asked/ba-p/2077594 

This feature is not enabled by default on each project, but it’s easy to turn on (if you have project permissions). Learn how to enable child-level planning for kanban teams. The roadmap uses the fields "Start date" and "Due date" to reflect the timeline bar schedule. 

For scrum teams, child issues are scheduled according to the sprint to which they’re assigned. On your roadmap, the schedule bar for all child issues is the same size regardless of their estimated duration, aligning with the sprints at the top header of the roadmap. You will need to have sprints created with dates to see them on the roadmap. https://support.atlassian.com/jira-software-cloud/docs/schedule-work-for-scrum-teams-on-your-roadmap/ 

If you have any queries or additional feedback you would like to provide via email or a zoom call, you can contact us here: jira-cloud-roadmaps@atlassian.com

Thank you,

Rathesh Richards, Product Manager, Jira Software. 

For my Jira Roadmaps I have to use the following fields: Start date and Due date to see the child issues of an Epic to show up on a roadmap.

My teams have been using Target start and Target end fields which did NOT show up on the Roadmap. 

@K. Ariga - 

Happy to help test when you make changes to fix this for relatively recent projects.

I have the "Schedule Child Issue" switch set for both a Kanban and a Scrum project, and I cannot schedule any other Issue Types, aside from Epic, on the Roadmap.

Appreciated your response Laura.

I am also having the same experience with Kanab type project that I can not explain. Only happening to new Kanban projects. 

I had something similar and it had something to do with where I'd created the sprints.  Since I hadn't created them from that board, they didn't show up?  but sometimes they do?  It's weird.  Don't forget you have to put dates on the sprints.

This is strange. I have some existing projects and the child scheduling is working well.

I created new two project, team managed, scrum & kanban, this feature doesn't seem to be working.
Anyone experiencing the same?

I even created a new project that was scrum and this does not work on my board.

Its beautiful!  Thank you!

It's not working for me on a Kanban board.

The setting is set.

It is out now, you need to set in roadmap settings:
https://community.atlassian.com/t5/Jira-Software-articles/What-s-new-in-the-Roadmap-view-I-m-so-glad-you-asked/ba-p/2077594?utm_source=product-announcement-email&utm_medium=email&utm_campaign=jswc-july-round-up_EML-13044&jobid=105659889&subid=1636276685#M710

I would also like to know the date of the release of this feature, please.

Thanks in advance to all the Jira geniuses for working on this feature; being able to see date range and dependencies at the child issue level on roadmaps decreases OUR dependency on external solutions for long-term capacity planning.

Hello,
I see in one of the comments above that this feature was scheduled to be released during the summer.
Sadly not being part of the Beta group, I would like to know if the expected release date is now known ?  

Thanks

if a story/task is assigned to "sprint 1" with dates 02/11/22 - 12/11/22, the story/task will be displayed that it will start and end to be delivered in that sprint timeframe.

Are there any plans to allow setting explicit start/end dates on child issues when using sprints? It works really well in Kanban mode.

Sprint duration can vary across teams/organizations and making all child issues the same duration makes it difficult to manage dependencies using the roadmap and visualise a sprint load properly.

In other words, when looking at the roadmap, all stories in the sprint appear to have equal weight/size.

Hi there - Thanks to those who raised the issue with the Beta no longer being active. 
This issue has now been resolved, and if you had access to the Beta before, you should see it active again. Please let me know if you do not see it. 

We apologize for any disruption this may have caused you and your team overnight, and hope you can continue planning and aligning on work together  

For those NOT in the beta group, never fear - we are close to a full release in July 2022 with a few changes in how the feature is enabled for your roadmap for the first time. 
We'll keep you updated on this ticket with the exact release date, and how to enable the feature on your instance. For those in EAP/Beta group, there will be no additional setup needed for your instance.

Thanks again, 

Rathesh Richards, Product Manager - Jira Software cloud. 

We were also part of the beta and now the feature has disappeared. It has lead to quite a bit of confusion with our team since the visualization of our child issues with the entire project is no longer available. Would appreciate re-enabling the feature or providing a release date.

I went through the survey again because we are no longer in the EAP for our project. Not sure why we don't have this feature anymore.

We use this feature daily and it was critical for our operations. Please re-enable this for us again or please provide a release date for this feature.

We were a part of the beta and it was going well and super handy to use, but not we're not? Can you please re-enable for us as we have many projects on the go and coordinating across them without this feature is very difficult.

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Any chance I can get added to the Beta pretty please ?

+1

+1

+1

+1

+1

+1

+1

This is so stupid simple to implement I'm really struggling to understand why it's not already a feature.

+1

+1

+1

It is very important to anyone who understands the importance of this functionality and have actually worked on projects.

Unfortunately those at Atlassian make changes that make no sense and are not logical rather than what the PAYING customer needs.

+1 

I see this issue very important. 

+1 

This is a must-have feature in my opinion. We are working on a project at the moment and are finding real issues with not having this feature enabled to show timelines for Stories and Tasks, and subsequent dependencies, on the Roadmap page. 

Is there any way that our organisation can join the Beta group please as we have a project we're prepping for at the moment that would greatly benefit from this feature?

Hi all - Thank you for your additional feedback and patience.

We’re happy to announce that our Early access Program for this feature went well, and the Kanban Story level issue planning feature is headed for Beta starting this week.

Participants for the beta have been chosen at random. If you’re part of the beta group, you’ll see a lozenge that reads Beta feature enabled and you’ll be able to plan child issues on your roadmap for Kanban teams. The feature requires no setup to use.

The EAP has now ended, but those who were part of the EAP still have access to the feature. The only thing that’s changed is the lozenge mentioned above.

Assuming the beta goes well, we expect to roll this feature (with some improvements) out to all users on all cloud editions in the upcoming months. As always, we’ll keep you updated on this ticket.
 
Thanks,
Rathesh Richards, Product Manager - Jira Software.