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
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
In the case when issues don't have start and end dates, the sprint dates are used. Those sprint date are "pre populated" but not actually stored in the issue.
Is it possible to "auto save" those pre populated dates in the issue?
Because we have a use case where the sprint dates must be displayed within an issue (view issue screen).
Hi @Berry Kersten ,
At the moment this isn't possible. The reason for this is that an issue can appear in multiple plans and each plan can have a different configured iteration length for the associated team. Therefore it's not possible to reliably set this data automatically.
I totally acknowledge that this is very confusing behaviour but is a result of the history Advanced Roadmaps (formerly Portfolio) and how it used to be a market place application. The ideal situation would be that the board containing the sprint would be also be associated with a specific team and have a fixed iteration length and then we could guarantee that dates would be inferred consistently. However, at the moment this is not the case.
We did explore the possibility of providing a bulk action within plans to allow you to apply the dates inferred from the sprint (as you can from dates "rolled up" from descendant issues) but that hasn't been implemented yet and we have no firm plans to add that.
When you run the Auto-Schedule tool within a plan it will apply the dates from the sprints but then you are relinquishing control of sprint assignment to the underlying algorithm.
I appreciate this isn't the answer you're hoping for, but I just wanted to be as honest as possible with you about the current situation.
Thanks for reaching out about this, unfortunately this isn't a priority for us to look at right now. Not because it wouldn't be a useful update, but simply because of the relative priorities of work on our backlog. Unfortunately this hasn't progressed since the original question was raised and it isn't likely to in the foreseeable future,
There is an explicit control for doing this, but it doesn't seem to do anything. Is there some additional configuration required to get the dates to populate in the plan?
Without this automation, it creates a lot of work to get your plan working if the plan has many tickets.