Issue with Sprints in JIRA for a particular project

[swati gupta]

Issues are moved from one Sprint to another even when the Sprint Is not completed (the issues not in Done status either move to Backlog or other chosen sprints when completing the sprint) and data is lost.

The problem could be that the Board used are Kanban boards which does not support the functionality.

The sprint ids also got lost in the project once the sprint is closed and says you do not have permissions to view the Sprint or it does not exists anymore.

Please be so kind to share your suggestions on the sprint/boards issue in JIRA and let us know if there are any changes made to the boards in new releases?

Please let me know if more inputs are required from my end in order to make the issue more clear?

Thank You!!

[swati gupta]

User has tried to use Scrum board instead of Kanban board but still the sprints are moving to another.

Can anyone help me?

Thank You!!

[swati gupta]

Hi @Nic Brough -Adaptavist- @ Sreenivasaraju P.

Can you please help me. Its urgent!!

[swati gupta]

Hi Atlassian Team,

Can anyone help me with the above issue? Its been quiet long and the issue still persists.

Thank you!!

[Nic Brough -Adaptavist-]

The answer has not changed - one of your people is deleting them.  Jira does not have any functions to delete without humans (or apps) doing it.

[swati gupta]

Hi Nic,

Thank You for the reply.

But no one is deleting the sprints and the issue is still the same that the data of sprint is moving to another sprint automatically.

Can you or anyone provide any other solution for the same?

Its very urgent to find out the reason for the same.

Appreciate your kind help!!

Thank You

[swati gupta]

@Nic Brough -Adaptavist- @Atlassian @[deleted] 

Can anyone help me with the Sprint issue? Its very urgent

Thank You!!

[Nic Brough -Adaptavist-]

There is nothing more I can help you with directly.

It's no good saying "no one is removing issues from sprints" or "no one is deleting sprints" - someone is.  There is nothing in Jira that would do it without a human triggering that action. (Although, it may be automated or scripted, it is still initiated by a human)

You need to find out who is doing it and stop them.

[swati gupta]

Hi Atlassian Team,

Can anyone help me with the above issue? Its been quiet long and the issue still persists.

Thank you!!

[Nic Brough -Adaptavist-]

I think you need to look at what is removing the issues from the sprints.

Jira will only move issues from one sprint to another when

• A sprint ends, and there are open issues in the current sprint
• A human, or human created automation/script, edits the issue and changes or removes the sprint data
• A human deletes a sprint

My best guess is that the people using your Kanban boards are editing issues in such a a way that it moves the issues out of the sprints they are currently in. 

For "sprint does not exist", that really does sound like people are deleting sprints.

What we really could use is an example of an issue to which this happens, and a look at the history of the issue around the time it moves sprint.

[swati gupta]

Hi Nic,

Thank You for your answer. But people are not deleting the sprints manually. 

It is weird that the sprint is closed the sprint id does not exists anymore. Earlier everything was working fine with the same board, same filters. 

But now sprints are showing different behavior.

Thank You!!