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; } } }

Advanced Roadmaps (Cloud) has shifted Sprints out of order

kevin.kowitski

I am pulling in sprints that are aligned to the same schedule and naming convention across different projects and boards. Aligning a single board to a single shared team. The system is successfully recognizing that the sprints of the same name from the different boards are intended to be executed in the same time period. However, the plan is shifting the sprints that were created on the board backlogs out of order, and then issuing a warning that they do not have the same dates.

I have tried to re-define the sprints, but the tool started doing strange things in the plan like creating duplicate sprints. Then instead of re-defining / renaming sprints, I deleted and started over building out the sprints. Still the same problem.

I have included attachments that show two different boards for two different teams. These teams have the same active sprint with the same start and end date. Both of these boards/teams have the same sprints built out in the same order in their backlogs. However, the plan has shifted the sprints out of order. Both Backlogs and Sprint Build Out.PNG Plan with Sprint Missing.PNG

Comments

Karl Hamilton_pa57n9

Sometimes when my plans are created, duplicate sprints are created until I assign the team using bulk update but I don’t know why.

i think it could be a problem with board filters In jira or issues having attributes making them appear on duplicate boards in jira before import to plans in advanced roadmaps.

does everyone have to assign teams In advanced portfolio before Sprint capacity icons appear?

Courtney M. Schkurko

Did you ever get an answer to this? The same thing is happening to me. I have multiple teams on a train sharing common sprints. The tool cannot recognize the order even though when I look at the backlog, the sprints are in the correct order by rank

Olga Plisko

The same problem happens in our plans. The sprint dates in the plan not the same as original sprint dates. The plan's sprints dates are shifted and plan has created additional (dummy) sprints. We use freshest version of Advanced Roadmaps in the JIRA Server 8.5 (enterprise) version.

Could someone from Atllasian team to answer and explain this behavior?

Dave

Just catching up with this thread as I got notified by the recent post from @Olga Plisko ...

To give some context around this it's important to understand that sprints are not tied to any specific board. If an issue on a board is assigned to a sprint then that sprint will appear on the board (so sprints can actually appear in multiple boards).

On more recent versions of Server / Data Center it is possible to configure the start and end dates of future sprints (this capability isn't available on Cloud yet) but typically only active and completed sprints have start and end dates.

When you include a board as an issue source in an Advanced Roadmaps plan it will bring in all the sprints that are associated with that board. Active and completed sprints will be rendered on the timeline using the dates that they have, but all future and projected sprints will be rendered based on their order on the board and the iteration length configured for the issue source.

A future sprint is any sprint that exists on the board that is neither completed nor started and a projected sprint is a sprint that is expected to be created based on the iteration length.

Due to the absence of guaranteed start and end dates on a sprint this can result in sprints appearing in unexpected positions on the timeline. This often occurs when an issue is assigned to a team that is not associated with the issue source from which the sprint assigned to the issue is derived.

You can also get duplicate future sprints appearing (sometimes with different lengths) in this case too - especially if the sprint is assigned to issues for different teams with different sprint lengths.

We'd typically recommend that you try to organise your work so that each team has it's own dedicated board (you can do this by sharing the team and using it in the JQL filter used for the board source and then using that board as an issue source that you associate with the team).

We're actually investigating making this much simpler - ideally, the iteration length and team associated with the issue source should be configured on the issue source itself. The way that it works right now is a result of the Advanced Roadmaps previously being a 3rd party application.

Hopefully this explains some of the behaviour that is happening. Please let me know if anyone needs any further clarifications or if it feels like their is a bug that needs addressing (although in the case of a bug it might be more efficient to log a support case).

Regards,

Dave

Motti Friedman_pcx8io

Hi Dave,

In our plan (I work with Olga), an active sprint appears on the plan with a different end date than on the board. The board is a simple filter of label in a single project.

After the altered sprint, we get a projected sprint that is followed by actual future sprints. It's a mess.

I would exepct projected sprints to only appear after the existing future sprints. Also, it would be great to be able to assign dates to the future sprints and fix the automated mistakes.

I do have two teams defined in the plan but they are defined by assignee and all are part of the same board.

Appreciate your insight

Thanks

Motti

Dave

Thanks for getting back to me with those extra details @Motti Friedman, that definitely doesn't sound like the expected behaviour. I would definitely recommend raising a support request to look into this as it is likely to yield a faster outcome, however if you want to share some screenshots of what you're seeing then that would be good, for example:

the active sprint on the backlog
the sprint on the plan (ideally with the sprint flyout displayed)
the configuration for the team associated with the board that the sprint appears on

Projected sprints definitely shouldn't appear before future sprints though. You should definitely ensure that the issues are assigned to the team associated with the sprint. Are you grouping by team or sprint to see the sprints on the timeline?

Regards,

Dave

Motti Friedman_pcx8io

Thanks for the quick response, Dave.

Here are a few screenshots: the plan showing projected "Sprint 5" added before future "Q1-21:Sprint6". The dates on "Q1-21:Sprint5" that are different in plan than in backlog.

We'll open a support ticket as well.

Thanks

Motti

Richard Cross_f74qtv

Aha - thank you for solving that particular issue for me!

:-)

Karl Hamilton_pa57n9

No problem Richard! :-)

Welcome!

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

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps

sprint

date

schedule

roadmap

plan

capacity