Due to the nature of my project, we have Epics that span multiple sprints, and we have Stories that will start and end during different sprints, or even more challenging we will have stories that we anticipate will kick off mid-sprint and end one or two sprints later. I am using the detail of Start Date and End date within the Story ticket to indicate these precise dates, but I have noticed that in the Timeline view, Stories can only be moved from one sprint to the next. Is there any way to have the Bar graph for a given Story in the timeline view accurately reflect the Start and Due date of that ticket?
Thanks!
Welcome to the Atlassian Community!
Epics are expected to span sprints, because they're made up of many stories.
But stories should not move between sprints. The whole point of a sprint is to deliver the stories that the team commits to doing in the sprint. If a story moves into the next sprint, the team has failed, and it's a trigger to look at why it failed, with a view to improving the process such that it won't happen again (or at least explaining why it failed - you can't change a process to account for unexpected events like sickness, production emergencies, accidents etc)
If you are planning to have stories move from one sprint to the next, then you are not using them properly. You would be better off moving to a Kanban process.
The Timeline view of sprints reflects the way things are supposed to be done with Sprints, there's no way to change that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.