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

A bug when closing a sprint and moving not done items to selected sprint

Michal H_vhq7ay

We face an issue from a few weeks(jira software datacenter). We have an active sprint (e.g. Sprint23) and a few future sprints created in a backlog (e.g. Sprint24, Sprint25). When we close the sprint we want to move not done items to another sprint (e.g Sprint24). We select that sprint during current sprint closure. What is suprising some of not finished items in the sprint (Sprint23) are moved to selected sprint (Sprint24) but also some of not finished items are not moved to Sprint24 (the field sprint is not updated for them). It was a few times what happened when we were closing Sprint(n) and moving not finished items to Sprint(n+1) and some not finished items were moved and some not.

Do you have any idea what could be the reason and how to fix that?

Is it a bug on jira side, have you ever experience that?

Accepted answers

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

For an issue to move into the next sprint when the current sprint, it must not be in the last column on the board. Is that how you are defining "finished"?

Also note that all of it's sub-tasks, if it have any, also have to be on the board and also in the last column, for an issue to be "done"

Michal H_vhq7ay

Hey @Nic Brough -Adaptavist- thanks, it is nice to be here, thanks for reply.

Just to clarify.
I don t want to move items finished in sprint, I want to move items not finished(open)
I mean items that are not in the last column, which means that are not done - still open during sprint closure.

For those items when closing sprint there is a message "Move open issues to" and options 'backlog', 'new sprint', and also a list of all created sprints in the backlog.

From that list we select existing not started yet sprint. All open items from closing sprint (items not in last column) should be moved to that sprint. It happens for 75% of open items. 25% of open items from closing sprint don t have field sprint edited automatically - they are not moved to the new sprint as it should be done.

I am pasting screenshots, please ignore number of items, it is just to show the feature where we experience that.

Really no idea why. Do you have any thoughts, thanks in advance.

Nic Brough -Adaptavist-

So how are you defining open and closed (where are the issues when you close the sprint)?

Michal H_vhq7ay

Hey @Nic Brough -Adaptavist- thanks for looking into that topic, really appreciate that.

I define that the same as everyone I believe: closed or finished - in last column during sprint closure (let s call it group A). Not closed, open - not in the last column when closing the sprint (let s call it group

The point is that my question concerns only group B and is not related to group A at all. I select the option to move open items to the selected sprint when closing sprint (please see screenshots). Some items from group B are moved to that sprint (the field sprint is updated for them - group B1) and some items from group B are not moved to the selected sprint (field sprint doesn t change for them - is not updated - group B2)

This looks like a bug. Especially items from B1 and B2 do have the same config - the same issuetype, project and status.

Grzegorz Olszewski

Hi,

We have observed such behavior that when closing a sprint and indicating the next sprint for open issues, Jira transfers to the new sprint only those issues that are visible on the current board.

Although the message shows the number of all open issues in the project, only those that match the filter of the current board are transferred to the next sprint, the rest go to the backlog.

This behavior can be considered more flexible (you can transfer only issues from the selected board to the next sprint), but the message about the number of transferred issues is misleading.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server