nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Future Sprint in Advanced Roadmap, 2 weeks in Advance

Mike Lemmon_8yw477

Hi There:

In Advanced Roadmap the first Future sprint after the Active Sprint is not dated to immediately follow the Active sprint, it seems to be dated an additional 2 weeks in advance .. almost like there is a Hidden sprint in between.

Any thoughts on what might be causing this?

Thanks for your help, it is always greatly appreciated.

Comments

Curt Holley

HI @Mike Lemmon

What are you using as the Issue sources? A Board, Project or filter? or a combo of/multiple sources??

Then for the board where the 2 sprints involve reside, what is the Filter Query of that board? Are there multiple active sprints, or multiple projects in scope of the filter query?

Dave

Hi @Mike Lemmon,

Are you on Server / DC or Cloud? On Server / DC it is possible to configure future start and end dates on future sprints (this isn't available on Cloud yet but is coming soon). That would be one reason for the gap appearing.

Regards,

Dave

Mike Lemmon_8yw477

Hey Dave .. thanks for responding .. much appreciated.

We are on the Server version.

I have been using Advanced Roadmap for several months now with no problems.

Now all of sudden the the first Future Sprint on the Road map is reflecting a starting date 2 sprints in the future...

In our Scrum Team Backlog there is nothing between the active sprint and the next one ..

Thanks, have a great day.

Mike Lemmon_8yw477

Hey Curt .. thanks .. please see my response to the post below...

Dave

Hi @Mike Lemmon,

Although there might not be a gap between sprints, it's still possible to create a gap by specifically configuring the start and end dates for a future sprint. Previously future sprint dates would be calculated entirely based on the order they appear in the backlog and the iteration length configured for a team in a plan (all relative to the active sprint or today if there was no active sprint).

However, now that you can give every future sprint it's own start and end date then the timeline in a plan will honour that.

So it's worth just looking at the next sprint on the board and checking to see if anyone has given it any specific dates.

Other than that, I can't think of any other reason why there would be a gap. You can get a gap after a completed sprint before another sprint has been made active - but you've said that the gap is after an active sprint.

Regards,

Dave

Mike Lemmon_8yw477

Hey Dave:

Dave when you mentioned "create a gap by specifically configuring the start and end dates for a future sprint. ".

I do not see how to do that in our Server version of JIRA, how is this done?

Thanks again .. have a great day.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

advanced-roadmaps