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

[Michal H]

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?

[Victor Mutambuki]

Alex,

On your project, are you able to see the Project Settings and/Or Project Summary (as shown in the attachment)?

Victor

[Alex Galisteo]

No, I just can see the following 3 options:

• Details: Icon, Name, Key, Access Type
• People:
• Features: Backlog, Srpints, ...

[Nic Brough -Adaptavist-]

Once a workflow is "simplified", it is locked down, as most changes aren't allowed.

You de-simplify by creating a new "workflow scheme" and applying that to the project.

[Alex Galisteo]

Thanks Nic,

But I'm unable to change the workflow. Is it possible to de-Simplify a project?

[Nic Brough -Adaptavist-]

Sorry, I should have emphasised this better in the first answer.  Yes, by creating a new "workflow scheme" and applying that to the project

[Alex Galisteo]

I understood.

But when I say I'm unable to change the workflow scheme I mean that for this project I don't have an option to do it (like I do have in all the other projects)

I only have 3 options in this project setup:

• Details: Icon, Name, Key, Access Type
• People:
• Features: Backlog, Srpints, ...

.

[Nic Brough -Adaptavist-]

Either you are not an admin, or this is a project created by an individual user for their own use (these can't be configured a lot, they always use simplified workflows, fixed fields etc)