Today I had an error message when closing the sprint and some issues went back into the backlog instead of moving to the next sprint (some issues went correctly into the next sprint).
Unfortunately, I did not had the time to read the error message as it disappeared very quickly...
I'd like to understand what caused this error but do not know where to look at.
Is there some error logs that I can access? Or any other place with useful information? I'm using the cloud version of JIRA.
Hi @Paulin Sanselme, Jira Cloud doesn't provide the ability to access application logs. You can track key activities on your Jira application by auditing it. That being said, if you still face problems, you would need to raise a ticket with the Atlassian support team (https://support.atlassian.com/contact)
If this is something you see happening very often, you can also try to capture and post it here so that we can assist you better.
Today I closed my sprint and all pending issues went into the next one without any errors.
I guess it was an internal error of jira cloud and that I will never know what was the issue.
Still. I guess I can consider this issue solved if it does not happen anymore.
for the core of your question Ivan already answered perfectly.
What might have happened in your scenario is that you had some incomplete issues and the following should have been provided for you to select:
If the sprint has incomplete issues, select from one of the following:
- Backlog, to move the issues to the backlog
- Any future sprint, to move the issues to any fuure sprint that's already created
- New sprint, to create a new sprint and then move the issues to the new sprint
This all just according to:
This is the normal behaviour - but when you say you received an error message you probably have the option to compare what is different from those issues? Likely something comes to mind what makes them special when looking at them - it might depend on your issues as such.
If nothing obvious is visible, contacting Support like Ivan said is a good choice indeed.
Sorry if I was not clear.
I chose the second option (move incomplete to next sprint).
Then I had an error message like "some error code : some message explaining the code" but it was displayed for a very short time and I failed to read it properly or to take a screenshot as I was not expected it.
Consequence : Some incomplete issues went to the next sprint as expected but some others went back to the backlog...
It was easy to find those issues with a bit of JQL and move them to the next sprint manually (as batch update the sprint value would replace the old sprint values instead of just adding one more sprint).
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events