Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Getting an Error without any Text during closure of a Sprint

Mesut Kiratli
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 2, 2020

Hi,

I am getting an Error when I close the Sprint and move the Issues to th next Sprint.

The Error box has no explanation, no Text, nothing. Just saying "Error" with a X (to close the Error pop-up window).

Here is more details:

1) I create a new (next) Sprint.

2) We go through the old Sprint and to the final updates if there are any. 

3) I hit "close sprint" 

4) a Window appears and asks what to do with the not completed issues. I select "move to the new Sprint"

5) I get this error message

 

I can't see the issues in the old sprint because apparently the "closing" part has been executed. Whjat has not worked is the movement of the issues to the new sprint. I see that the issues has landed in the Backlog. It is extremeley difficult to select them out of the hundreds of the issues that are in the backlog.

Here is my workaround that causes loss of historic information:

6) I select all the "not completed"  issues that have the old Sprint in the sprint field

7) I do mass update 

8) I enter the new Sprint ID in the sprint field and update the issues

 

After this, I can see the issues in the new sprint. Then we add some new issues to the sprint and start the Sprint with its new scope. This mass update overrides the field Sprint with just the value of the new sprint, while I want to see if we have issues that we carry with us for many sprints (please, no discussion here about "if you have such long stories, you are doing wrong somewhere else" and so on... it has its reasons and has nothing to do with a software bug of jira )

Atlassian/Jira support guys: any explanation? any help?

Anyone else who have faced this problem? any help?

 

cheers

Mesut

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events