-
Suggestion
-
Resolution: Fixed
-
7,054
-
Hi all,
Thank you for your patience throughout this time. The ability to schedule child/story-level issues with dates is now available for Kanban projects on Jira Software Cloud on Free, Standard, and Premium editions.
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).
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.
The feedback that you’ve given here or through other channels has been invaluable in informing our product planning.
- We have provided functionality for scrum projects (existing behavior).
- Once you expand the epic, you will see the stories/tasks and any existing dependencies. If you have scheduled (with dates) sprints in the backlog, the sprints will be displayed in the header of the roadmap. If the story-level issue start/end date has been assigned to a scheduled sprint, each issue will automatically display on the roadmap in alignment with the sprint dates it is assigned (and not from the start/due date fields, if they are being used).
Example: 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.
Given Jira Software is an Agile project management tool, this follows closely with the Scrum framework, where work is scoped to be delivered within the timeframe of a sprint. https://support.atlassian.com/jira-software-cloud/docs/schedule-work-for-scrum-teams-on-your-roadmap/
- Once you expand the epic, you will see the stories/tasks and any existing dependencies. If you have scheduled (with dates) sprints in the backlog, the sprints will be displayed in the header of the roadmap. If the story-level issue start/end date has been assigned to a scheduled sprint, each issue will automatically display on the roadmap in alignment with the sprint dates it is assigned (and not from the start/due date fields, if they are being used).
-
- For Kanban projects, this is currently not possible to show the explicit dates for the child issues. We are currently working on a solution in BETA. Only participants in the current BETA group have the ability to schedule stories/tasks using explicit dates for Kanban projects. Please keep in mind that planning and scheduling issues from the Roadmap not only affects the Roadmap view, but also flows onto the board and backlog. We are gathering the feedback from the wider BETA group to make sure that the dates set, do not impact the development team's existing processes within Agile. We hope to make this available for all Kanban projects on all editions of Jira Software Cloud (including free and standard) by the end of July.
If you would like to provide specific feedback or chat over a zoom call about your team needs, then feel free to email our team at: jira-cloud-roadmaps@atlassian.com
Rathesh | Product Management, Roadmaps.
Problem
Currently, we can see only the date range for Epics that doesn't include the start and end date of the child issues.
Suggestion
Add the date range separately for each child issues.
- duplicates
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
JSWCLOUD-18798 Nex Gen Project View : Stories, Tasks, and Subtasks should be included in Roadmap view
- Closed
-
- Closed
- relates to
-
- Closed
-
- Closed
-
- Closed
- was cloned as
-
- Gathering Interest
- Mentioned in
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-91581] Date range for child issues on roadmap
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
I second the comments by Nora and Collin:
There is little added benefit in having sub-tasks simply mirror the duration of the sprint.
It would be ideal if their duration bars would be displayed independently of the sprint duration.
I hope you will consider this in a future release.
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!
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!
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).