Forums

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

"Done" issues/stories automatically moving to next sprint after closing current sprint

Michelle Sullivan November 5, 2019

We have inaccurate behavior with issues when closing a sprint.

Our "Done" status is in green color and last in the workflow.

When I close the sprint, some if not all issues automatically move to the next new sprint.

I've reviewed issues and can not find any common trend to explain the erroneous behavior of Done issues.  Subtasks are also in Done status 

 

3 answers

2 accepted

1 vote
Answer accepted
Leo
Community Champion
November 5, 2019

Hi @Michelle Sullivan,

Along with @Hernan Halabi - Elite IT Consulting Group answer  Done/final status of your issue should be mapped to the final column of your scrum board

 

BR,

Leo

Michelle Sullivan November 6, 2019

Please provide steps to check the mapping of "done/final status of my issue".  I need to share steps with my team member so he can verify or fix the issue.

Leo
Community Champion
November 6, 2019

Board --> Configure --> Column 

Done/final status should be in the last (right most) column

Michelle Sullivan November 6, 2019

Can we jump on a Skype call?

Michelle Sullivan November 6, 2019

my skype - sullivanm22@wawa.com

Leo
Community Champion
November 6, 2019

ouch, I'm not active in skype :( 

Michelle Sullivan November 6, 2019

TEAMs?

Michelle Sullivan November 6, 2019

What do you have access to?

Michelle Sullivan November 6, 2019

My board shows this:

https://wawaappdev.atlassian.net/secure/RapidBoard.jspa?rapidView=161&projectKey=DTEDP&sprint=293

My Sprint 3 shows this:

https://wawaappdev.atlassian.net/secure/RapidBoard.jspa?rapidView=129&view=planning.nodetail&selectedIssue=DTEDP-181

  1. Please advise steps to remove Done stories from current Sprint 3.  The Done stories are from Sprint 1 and 2 and appeared only after completing Sprint 2.
  2. Please provide step by step to remove Done stories from current sprint and to prevent this from happening again in Sprint 4, once Sprint 3 has finished.

I look forward to your response ~

Regards,

Michelle

Leo
Community Champion
November 6, 2019

When Jira will move issues/stories to next sprint on current sprint close/complete?

>>> the open issues, according to Jira status does not matter instead Resolution Field. Resolution field should have some value apart from "Unresolved" and the current status of the issue should be mapped to final column of your scrum board

How to prevent the Done issues move to next sprint?

>>> should validate above mentioned points both resolution and final status of the issue(in board columns)

 

can you share me the screen shot of your board's column configuration view and Done issues's detail value(especially with resolution field)

Michelle Sullivan November 6, 2019

Yes I can share, which format is needed to share?  

Leo
Community Champion
November 6, 2019

any image format is fine. just want to view your board configuration and Done issue's resolution value

Michelle Sullivan November 6, 2019

See screenshot attached

Michelle Sullivan November 6, 2019

seems I can not attached screenshots here in word doc format.  Please advise email address I can send screenshot

Michelle Sullivan November 6, 2019

Not able to share board unfortunately

Leo
Community Champion
November 6, 2019

I'm attaching my screen shots for your referenceboard-column.pngstatus&resolution of issue.png

Michelle Sullivan November 7, 2019

thank you I will share with my team member and revert back if it fixed the issue 

Michelle Sullivan November 8, 2019

Thank you I've shared your screenshot with my team member Rob, he has responded with "

I’m not able to get the Resolution text to show up on a story.  In the story field config  screen it says it’s enabled, but I can’t seem to find it."

Please advise next steps

Michelle Sullivan November 8, 2019

Please see screenshots of Boards for reference. 

https://wawaappdev.atlassian.net/wiki/spaces/DD/pages/330958478/Meeting+Notes+page

MDM board looks fine.  But the EDP board, EDP and MDM Product Sprint log lists show DONE stories from sprint 1 and 2.

 

Please review screenshots and my team member's response, "I’m not able to get the Resolution text to show up on a story.  In the story field config  screen it says it’s enabled, but I can’t seem to find it."

If your not able to see my screenshots lets use an alternative email address or if you have a way to share desktop on Skype let's connect ~  My user name is sullivanm22@wawa.com

I look forward to your response. 

Leo
Community Champion
November 10, 2019

I'm not able to view your screenshots, you can send me your screen shots here: leoforatlas@gmail.com

Leo
Community Champion
November 11, 2019

And if you are on the cloud you'll see resolution value near to status like below screenshot resolution-in-cloud.png

Michelle Sullivan November 11, 2019

My view does not show resolution value "Won't Do".  How can Atlassian support work with me through SKYPE to bring issue to resolution today?

Leo
Community Champion
November 11, 2019

"Won't Do" is my resolution, you may see some other value there instead of won't do

it's better to go with atlassian support 

Michelle Sullivan November 11, 2019

How do I configure system to "Won't Do" to move previous Done stories back to sprint 1 and 2?  Our sprint 3 will end this week and I would like to reports to be as accurate as possible, but with the Done sprint 1 & 2 stories in the sprint, reports are skewed.

 

I can be available to address this issue with a resolution.  Can we connect by phone or can you share step by step how to resolve the issue?

Michelle Sullivan November 11, 2019

Thank you for all your time and assistance Leo, I think I figured the issue out......

0 votes
Answer accepted
Michelle Sullivan November 6, 2019

What do you have access to?

1 vote
Hernan Halabi - Elite IT Consulting Group
Community Champion
November 5, 2019

have you checked that the issues have a resolution? it's important that it's the case. Jira considers issues as closed based on the fact that the ticket has a resolution not the ticket status.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events