Jira with Status done are showing in the next sprint

Rogerio
Contributor
May 24, 2018

Hi,

I have two Jiras with Type equals to "Support Issue" and Status equals to "Done" and Resolution equals to "Unresolved". When I close and open a new sprint, JIRA # 3142 goto move to Sprint 44, JIRA # 3076 stay in Sprint 43. If both are the same type and the same status, why did the 3142 goto move to Sprint 44?

I have other few jiras with different type that were with status done or won't do and were moved to Sprint 44, and other jiras with the same type/status that did not move to Sprint 44.

What I have analyzed so far:

The Status Done/Won't do are my last column in my Dashboard.

The Done status is "green" which is done I believe.

 

Am I missing something? What I should take a look? Why did one jira moved to Sprint 44 and the other stays in 33?

I try to take a look in the Activities to see if it was changed by mistake but I could not see anything there. Both JIRAs has a history of "Status To Do [ 10403 ] Done [ 10102 ]" 

Thanks in advance.

2 answers

1 accepted

0 votes
Answer accepted
Rogerio
Contributor
May 24, 2018

Sorry my mistake, these jiras were open before I close the Sprint, then I closed the sprint I said yes to move the jiras to the next sprint. Then when we were doing our sprint planing we said we won't do it our we notice that it was done. Then when I open a new Sprint those JIRAs that we said that were done/won't do show up and I thought it come over, but actually because I said yes in the first time, those jira had a sprint 44 on them before I even open a new sprint.  I guess, what I have to do is to remove from the Sprint when we said it is done/won't do, before we were changing the status and thinking that is enough.

0 votes
Nguyen Tran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 24, 2018

I'm thinking it's because of the resolution. Check if the resolution for #3142 is different from #3076. Seems like #3142 resolution is unresolved and #3076 is already resolved. Unresolved issue will be automatically moved to the next sprint.

Rogerio
Contributor
May 24, 2018

Thanks for answering, I guess it was an error from our part. btw the resolution were the same for both. :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events