I believe this issue is a duplicate of JSWCLOUD-12169 – In Configure Board, allow multiple "Not Started" (Grey) and "Done" (Green) columns

Note, JSWCLOUD-12169 is the team-managed version of the ticket.  You may also wish to vote on the company-managed equivalent JSWCLOUD-18939 – In Configure Board, allow multiple "Not Started" (Blue) and "Done" (Green) columns

I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!

I feel like there are several different versions of this request... with the same intent.  We want some control over how the burndown/burnup reports calculate "done". 

Here's another that should probably be in the linked issues for this one:
https://jira.atlassian.com/browse/JSWCLOUD-16404

This has been in consideration for over 2 years - what's the status of this? 

We consider an issue done when it's deployed to production, which almost never equals the same time when a sprint is completed (i.e. sprint is closed on friday, deploy to production is done Tuesday after - rendering a sprint to never be considered "done" by Jiras defenition, making the reports essentially useless. 

This is kind of done in that you can mark a workflow status as belonging to the "category" Done and that can have its own column in the board, but the problem is that for the purposes of the burndown chart it doesn't consider those in Done category "Complete".

https://getsupport.atlassian.com/browse/JST-661084

On my next-gen project board, we have a status "Design Ready" which means the task is Done, also we have the status "Descoped" which means the task was cancelled.
Thus, we need two done statuses in the next-gen project to manage these two issues status. Otherwise, only the last status in the board is being considered as done, and the other status is being considered as in progress, migrating to the next sprint as pending, which is not true.

We track issues that we have made a decision not to complete but what to remember that we made the decision.  We'd like to go back to lane on our board for an 'icebox', but since tickets aren't done until they hit the right-most lane, we're stuck using tags for the 'icebox'.  The result is a lane full of tickets some of which are done and others that will never be done.  We'd like multiple lanes to be considered 'Done'.

This is so important. If you aren't going to implement Resolution reasons, there has to be a way to close a case without indicating that the work was done. 

Seconded. We have a "Peer Review" column that is currently an "in-progress" state, but we would like it to be an initial "done" state instead. This is because often our peer review occurs in batches. Semi-related, it would be nice to have a "cancelled" state. We're currently deleting issues that we would rather have marked as cancelled for keeping the paper-trail.