Sprints having same names are getting Closed Automatically.

Users have reported that their sprints are getting closed automatically.

The only difference from other users is that they are having sprints with same names, like Sprint 50 with 3 different dates, then Sprint 51 with different dates etc.

As we are on Ondemand, we are unable to trace out, what exactly has happened with that Sprint and who has closed that sprint. Atlassian was only able to provide IP address in the logs and which wasn't useful for tracking the user.

Difference w.r.t other projects:

1) Project has more than 15000 issues

2) This project has more than 15 Scrum boards

3) Project has used same Sprint Names with different dates

My question, is there anyway to findout what exactly could have happened and who has closed the sprint ??

Is there anyway to restrict access for closing sprint ??

Does having same names has any adverse effect ??

Does JIRA re-indexing has anything to do ??

2 answers

I've had the very same problem this morning. Any news on fixing this???

We are experiencing the same issue. Please advise what is causing this. We are running Jira 6.2.4 downloaded and Jira Agile 6.3.13.1

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Agile

What's new this quarter in Confluence Server - August 2018

Hello Atlassian Community! My name is Ada , and I'm the Product Marketing Manager for Confluence Server at Atlassian. If you missed   our last post, we're transitioning to quarterly updates&nb...

163 views 0 1
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you