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

Problem when start a sprint...

Jeferson Sisto

Today I had to start a sprint. However, the burndown seems a little strange... there's no had the tendency line...

Today all my issues already be in the sprint before it started, however, after I click in the button to start, the Jira said that the issues were added AFTER the sprint started and the burndown turned strange...

What can I do? I deleted and started the sprint for many times and the result was the same.

Sprint A.png Sprint B.png

Accepted answers

Benjamin_tmh9yg

Does anyone else have permission setup to add to the sprint? If that's the case, you may encounter this problem.

Also, you mention strange, please add more details so that the community can lend additonal guide or information.

What did you mean by delete sprint? Do you mean you click on complete sprint or deleted from the backlog? To actually close a sprint, you must click on complete.

All comments

Benjamin_tmh9yg

Does anyone else have permission setup to add to the sprint? If that's the case, you may encounter this problem.

Also, you mention strange, please add more details so that the community can lend additonal guide or information.

What did you mean by delete sprint? Do you mean you click on complete sprint or deleted from the backlog? To actually close a sprint, you must click on complete.

Jeferson Sisto

Hi everybody! Thanks for attention!

Please, take a look at the attachments... there are two images.. an image refered the sprint "2020-05-A" and another refered the sprint "2020-05-B".

When I started sprint "A", all issues were "inside" the sprint and the burndown was correctly created.

When I created the sprint "B", all issues were also within the sprint, but the burndown wasn't correctly created. It seems like Jira "added" the issues AFTER the creation of the sprint but it isn't true. All issues had already been related with "B" sprint.

Why?

Benjamin_tmh9yg

Thanks for the pictures.

1. Check issue history to see who has added to the sprint.

2. Also, if the sprint time was configure to start earlier time than when the issues were added, this could happen.

I'm thinking the later might have happen.

Complete the sprint. Add the issues to the sprint. Note down the sprint start time and make sure it's adjusted to the current time.

Jeferson Sisto

Yep... I did what you said and everything worked!

Thank you a lot!

Jeferson

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software