Forums

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

Complete sprint for status 'Done' or for statusCategory 'Done'

Adrian Peiu
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!
March 20, 2018

Hi,

 

I am looking at tuning my team's JIRA Agile project and at the moment

I have allocated Status Categories to my workflow statuses and I'd be interested in understanding how these will affect completing an active sprint. 

 

Specifically, will selecting 'Complete Sprint' count issues having status = 'Done' or status Category = 'Done'?

 

Thanks in advance

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
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.
March 20, 2018

The definition of Done for a board is "issue is in the far right hand column on the board".

Status does not matter beyond the mapping into the right hand column, and status category is irrelevant.

Adrian Peiu
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!
March 20, 2018

Brilliant! Thanks for the quick response.

kristine.daniels
Contributor
March 14, 2023

I realize this is 5 years old, but I have a status "Ready for Release" in my far right column that is still getting carried forward to the next sprint. 

These are closed as far as the development team is concerned, but not for the product.  We only close issues once they are released to production.

Sprints seem to be controlled by statusCategory.  Would glad to learn otherwise.

Nic Brough -Adaptavist-
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.
March 14, 2023

Sprints are still controlled by the last column on the board.

Could any of your issues have open sub-tasks, or could you be having status beyond "ready for release" that are not mapped on to the done column?

kristine.daniels
Contributor
March 15, 2023

Hi Nic, I appreciate the response.  If you can shed light, this is my scenario.  When dev/test work are complete, Jiras are put in the "ready for release" status.  As far as sprint planning is concerned they are done with these tickets and don't want to see them again.

Our release to production process is not sprintly though, so it can take a while before the tickets are placed in a closed status.  If possible, I want these "ready for release" tickets to have a status category of "in progress", but NOT be carried forward to the next sprint.

When I put "ready for release" tickets in the far right column, the sprint reports consider them as completed work, but they still get carried forward.  Do you know if I can have a status with the "in progress" status category that doesn't get carried forward to new sprints?

Nic Brough -Adaptavist-
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.
March 15, 2023

Again, the status category is irrelevant.

Could any of your issues have open sub-tasks, or could you be having status beyond "ready for release" that are not mapped on to the done column?

kristine.daniels
Contributor
March 17, 2023

Looking deeper into the boards.  So far I've seen linked tasks, but no sub-tasks.  I don't think that linked bugs/tasks would be factor, right?

Nic Brough -Adaptavist-
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.
March 18, 2023

No, issue links should be irrelevant.

The only things that matter to sprint completion and carry-over are open sub-tasks and being in the last column of the board.

I think we need to see the details now - an issue that was carried over when it should not have been, with it's history, the board config (column configuration and board filter) and a view of how it looks on the board it's carried over into.

Like • Nas Raja likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events