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

Spill over user story to next sprint

harshvardhans

Hi,

Can some one suggest if there is any option in JIRA to Spill over a user story to nxt sprint without being removed from current sprint.

I can move the user stories from one sprint to another but doint so will remove the user story from current sprint and I will not be able to track it in the current sprint for reporting.

Accepted answers

Ste Wright

Hi @harshvardhans

When you close the open sprint, Jira will ask what you want to do with the open issues within it - either move them to the backlog, or to another future sprint.

That way, you can have an issue that has been in multiple sprints. Don't remove it from the open sprint, wait until you close it!

See more about completing sprints on this page.

Ste

All comments

Ste Wright

Hi @harshvardhans

When you close the open sprint, Jira will ask what you want to do with the open issues within it - either move them to the backlog, or to another future sprint.

That way, you can have an issue that has been in multiple sprints. Don't remove it from the open sprint, wait until you close it!

See more about completing sprints on this page.

Ste

Sheen Kaul

Hi @harshvardhans

You can update the sprint no when you edit/open the ticket.

Kasey C

Hi @Ste Wright

May I ask if I don't want to close the sprint, is there other way to move the issue to another sprint but still be able to have the spillover record when I export a burndown report?

Thanks.

Nic Brough -Adaptavist-

Yes, you can move the issue to another sprint, you can drag it around in the backlog view.

But, don't. It makes nonsense of your sprint records and velocity. Your burndown report will be inaccurate.

You should close the sprint and let the issue "spill over" normally.

Sarah Dagher

Is there a way to manipulate the default setting in order to place the spillover at the top of the next sprint while maintaining the order of the card?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland