I need the equivalent of a "Done" Status that is not the actual "Done" status

[Jon Behm]

I need to add a new status that is the functional equivalent of the "Done" status to our workflow. I need stories/bugs assigned to this new status to stay in our print but appear as "Done" for reporting purposes. 

I have experimented with some of the canned statuses but every one I have tried makes the story/bug disappear from the sprint when it is moved to that status. Resolved removes it. Ready for Production removes it. Hoping there is something (other than Done) that will keep it around for visibility purposes. 

Can anyone help? Thanks!

[Joe Pitt]

In the standard model if it isn't resolved it isn't 'done' You need to create a status that doesn't set the resolution, but is mapped to 'done' in your board. However, I expect that will cause confusion with the users. Without a resolution the assignee will see them in their assigned to me filter. Why do you want them to be considered done, but not really done? 

[Jon Behm]

We need a status that is basically Product Owner Review but we cannot have that status fall into the "In Progress" lane as it would with a normal workflow. For reporting purposes our work needs to be set to done prior to PO review. Our PO is external and we can't be on the hook for closing out stories/bugs until they get a chance to review them. I know that this is not normal or how Scrum should function but we're trying to mange with the situation we have. 

Can I create a new status that doesn't have any automatic actions tied to it and put it in the "Done" lane? I don't see any area for creating a new status that isn't one of those available from the dropdown. 

Thanks,

[Joe Pitt]

You can add another  column and map a new status to it. However you say the work has to be 'done' before the review which is the problem I see in your workflow. If the customer is reviewing it then I would say it isn't done until they approve it. I would add a column for customer review after in progress and before done. What are the options if the customer doesn't approve it? Can they send it back for rework? If approved you could have them move it to done and set the resolution in a post function.  See adding a column below:

https://confluence.atlassian.com/jirasoftwareserver/configuring-columns-938845277.html 

[Jon Behm]

The reasons are a bit complicated but yes, I realize our workflow is unorthodox. Basically we ran into a problem which was a very busy PO who got behind on reviewing completed work. And that PO is also our client. So we completed our work but would have a velocity of zero until the PO could get around to officially approving everything, making for difficult situations. 

Thanks for your help!

[Jon Behm]

Hmm, created a custom workflow and placed it in the Done column but unfortunately it too is removing the stories/bugs from my sprint when selected. Any idea what I need to do @Joe Pitt?

[Jon Behm]

Or maybe you could tell me this: why is "Done" a unique status in that it seems to be the only one where if you select it the story/bug gets crossed out as opposed to disappearing from the sprint? Is there something I can do to recreate that functionality in a new custom status?

[Jon Behm]

What seems a little crazy to me is that my new custom status, which is in the "Done"column doesn't actually count stories as being done. It removes them from the sprint and for all intents and purposes treats them like they are actually Cancelled.  

[Victor Mutambuki]

Jon,

Complete/Resolved?

Victor

[Jon Behm]

I tried Resolved but that actually makes the story/bug disappear from the sprint. I suspect Completed will be the same but am hoping to figure this out without having to trial and error every status as it gets messy