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 ??
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
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.