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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I would like to organize the child-level issues with their own dates.
As you see below, the first schedule is the epic (this one I can move to a different date than the sprint)
The second one is scheduled to start on the 24 and end on the 31, but the roadmap takes the date of the sprint.
How can I have the dates of the child-level issues free from the dates of the sprint (within the sprint they belong of course)?
Hello @Samuel Rodriguez
Welcome to the Atlassian community!
As per the Roadmap documentation that is how scheduling works for a roadmap associated with a Scrum board/project. The dates for the issues will be taken from the sprints to which they are assigned. You can't use issue specific dates.
If you want to use issue specific dates that can be done only with a roadmap associated with a Kanban board/project.
EDIT 21 April 2023
As of changes released between March 27 and April 2 it is now possible to use issue specific dates rather than Sprint dates for scheduling issues in a Scrum board in the Basic Roadmap, as noted in this Blog Post about changes made between March 27 and April 2.
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.
@Trudy Claspill Your answer is incorrect.
"Child-issue" planning is available for a Scrum project, but it must be enabled by changing a default.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<EDITED>
Actually, I simply reiterated what the documentation said. At the time I wrote the answer I don't think it said anything about being able to use Start and Due dates for issues in a Scrum related Roadmap.
I see that now it does.
I see that change was implemented after I posted my answer, as noted in this Blog Post about changes made between March 27 and April 2. Thank you for alerting me to the documentation change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy ClaspillAre you able to remove or edit your earlier answer? (Especially since it has the "Accepted Answer Badge". It would be better to make sure people see the current information.
Thanks,
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Done. Thank you for the suggestion.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.