Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Issues marked as Done still appears in a New Sprint

We configured our workflow so that we have have a status of Deployed (for code that has been successfully tested and deployed). This status is mapped to a category of Done in the status definition screen. We also have status of a Closed in the workflow, for issues that are resolved for other than deployed status. This status is also mapped to a category of Done.

The problem that we're having is that when we set the status for an issue to Deployed, we're expecting these issues to drop off when we create a new sprint since these issues were resolved from the previews sprint. 

How do we get this to work?

5 answers

7 votes

A board and sprint's definition of done is "in the far right hand column on the board".  The status and category do not matter beyond the status being in that column.

Make sure "closed in the workflow" and "deployed" are included in the last column.

Make sure "closed in the workflow" and "deployed" are included in the last column.

It seems there's more to this than that. Our rightmost column is just called "Done" and issues marked as "Done" are moving to the next sprint. (We have it set so that there are different resolution options when moving an issue to the right most column, but that only affects the "Resolution" field which you said doesn't matter).

Like maria likes this

Do the issues that move have sub-tasks that are not also in the done column?

Like Paul Klapperich likes this

When issues have incomplete sub-tasks we get an error and can't even attempt to close the sprint. ("Sprint cannot be completed as there are incomplete subtasks on the following issues...")

But you pointed me in the right direction. It was the opposite; there were a couple of large parent tasks in the verify column who had all of their subtasks in done. Thanks!

Like Laurent Bierge likes this

Ahh, nicely spotted.  Sub-tasks are not the obvious one to think of, but I'm glad I helped you find the missing issues by mentioning them!

Like Paul Klapperich likes this

Create two (or more) Boards: First board is your current board with columns for all steps of the workflow showing. This is for the team's day to day issue management. Create a second board with all 'Resolved' issue statuses (i.e. Deployed and Closed) in the last column. Use the Second board specifically for closing sprints. This will ensure story points for all resolved issues are accounted for in velocity and sprint reports, while having the other board to show all statuses clearly.

The solution is as follows:

  • Ensure your "Deployed" status is mapped to the far right column of your board
  • If you actually don't want to see those completed/done issues any more on the board during an active sprint, edit your board's Filter query to exclude issues in the status Deployed ( " AND Status != Deployed ").

Once you move them to this status, they will disappear from the board, but as they are technically mapped to the far right column, they won't be carried forward to the next sprint :-)

Thank you.   

Do you add a resolution to the ticket when it is considered 'done'? Without a resolution, Jira keeps the ticket open... 

0 votes
Moses Thomas Community Leader May 29, 2018


in-addition to  previous  comments,

make sure that  active sprint is completed.

if not  go  to   active sprints  >  complete sprint   they should disappear and you can view them in reports.



We have the same set up and problem. Last two columns of the board are for issues that are 'Done'. When moving issues into 2nd to last workflow step, the resolution screen comes up and tickets are marked with a resolution (i.e. Done, Won't Do, Cannot Reproduce, etc.). There is no change in Resolution status when moving into the last workflow step.

When I click Complete sprint on the Active Sprint page, I would expect all issues with a Resolution (i.e. Done) would drop from the sprint, but they roll over to the next sprint. This causes Done issues to be in the new sprint and not credit these Done tickets to the velocity.

We don't want to put two states in the last column because we lose visibility of this status and cannot drag between columns.

As before,

A board and sprint's definition of done is "in the far right hand column on the board".  The status and category do not matter beyond the status being in that column.

The resolution is also irrelevant.  Look at the "done" column.

Does any one found the solution for this yet. I am also facing the similar issue.




There is no solution beyond moving your 'done' column to be the far most right column

Sadly, a board and sprint's definition of done is "in the far right hand column on the board".  A strangely arbitrary and fixed definition for JIRA, given its flexibility is its real power. 

So issues will be carried forward (even if in a 'done' status and Resolution=Done etc) unless they are in the far right column.

Thanks @Carl Screwvala  for response- At present to move forward, i have also used the work around to move 'Done' column rightmost. 




I ran into this issue recently when I decided to introduce several new Done Status Category types.  When is this going to get fixed, because this is poor design?

Especially when you consider that everywhere else in Jira the new Done status types are properly recognized natively and by plugins.

This includes Jira showing the custom Done status types with a green checkmark and the new types recognized properly when queried in filters.

I'm stunned this design issue has been around this long.

There is no issue or bug here. 

Jira has always defined at the last column on a board as "done".  That's how boards work.

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

72 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you