Unable to Close down a Sprint

[Karl Samson]

Hi all, we have happened upon a strange unexplained issue with not being able to close down a Sprint manually. When we do, we are able to click the 'Complete' button, but nothing happens, no error message either!? We can set the system to automatically close a sprint, which may be a clue?

We have checked Sprint Permissions, overlapping Sprints, Board Filter issues, unresolved issues, but nothing has changed or is awry. The only thing that has changed is we upgrade from 10.3.16 to 10.3.18 (Jira DC). We will be checking Dev Tools for 403, 401 errors on Friday, when the latest Sprint we are working on ends, but any suggestions welcome, before I raise an Atlassian Support ticket.

Thanks & regards,

Karl.

[John Funk]

Hi Karl,

Outside of trying a different browser or trying with Incognito or Private window mode, I would say go ahead and open a support ticket. 

[Karl Samson]

What I forgot to mention is this isn't an issue in our Pre-Prod environment, which is on the same version.

[John Funk]

That's weird - you should probably go ahead and open a support ticket. 

[Karl Samson]

I think this is what we will have to do, but having done some more research, I have updated our 'Banner Announcement', as we noticed that the HTML, although working, was technically incorrect, and could be causing the Sprint 'Complete' execution to hang?

We will re-test closing a Sprint again, at the end of the week. 

[John Funk]

Very good - let us know how it goes. 

[Arkadiusz Wroblewski]

Hello @Karl Samson 

The part I would focus on is that auto-managed sprint completion still works.

That tells me Jira can still complete the sprint, so I would put the usual “unresolved issues / subtasks / sprint destination” checks lower down the list. Atlassian’s docs actually say auto-managed sprints won’t complete if there are closed parents with open subtasks, and they also explain that auto-managed completion runs as a Jira service job. 

So I would split it like this:

1. if manual completion works for a Jira admin, this is likely a permission / origin-board / board-filter scope problem for the acting user
2. if it fails even for a Jira admin, this looks much more like a UI/request-path regression after the 10.3.18 upgrade

I know sounds dumb but please check double if your User have Closing Sprint permissions on all Projects from which Issues coming.

If admin also cannot complete the sprint manually, I would go straight to Atlassian Support with those timestamps and logs.

Check the browser Network/Console at the exact moment you click Complete, and then match that timestamp against the Jira application logs and reverse proxy logs. If the button click returns nothing visible in the UI, I would specifically look for a hidden 401/403/500 or a JavaScript error

[Karl Samson]

Completing a Sprint manually is instance wide for ALL. So I think we will end up recording a HAR file, showing a possible 400 error?

But having done some more research, I have updated our 'Banner Announcement', as we noticed that the HTML, although working, was technically incorrect, and could be causing the Sprint 'Complete' execution to hang post upgrade?

We will re-test closing a Sprint again, at the end of the week.