Track a 'Done' issue through the deployment pipeline

[dtlhlbs]

Our Jira project has stories for both client/server applications and uses Scrum, with a Kanban board for each sprint. We use Versions to track the slower moving client releases but server releases are happening all the time.

We use 'Done' to mark the item as Done in development, ready for deployment to UAT, then production as required. However, Done server items disappear from view after the Sprint is complete, even though we still need to track the deployment. Any suggestions on how best to track items ready for deploy to UAT and/or production? Versions are not that useful for the server application - as every story would result in it's own version since we deploy frequently. I'd also like to avoid having new Kanban columns for UAT/Production status, especially since the item is done, just not deployed, so it should be off the sprint and into it's own release management cycle.

[Marty]

Hi David,

I am not on the Jira team, but I will try to help.

My first thought is that Done issues will be considered truly 'done' when you complete the Sprint.

So, if you want issues to be "long-lived" across sprints, you need to prevent the issue from entering the Done state.  You could do this by creating another status that means 'Done' for you but doesn't signal to Jira that the issue is truly Done.  Let's call your custom status 'Complete'.

My second thought would be to create multiple statuses that all are reflected as 'Complete' on the board but are actually different statuses.  You could have statuses 'Dev Done', 'UAT', 'Production' all map to 'Complete' in your board configuration.  So you only have one column, but multiple statuses.

I hope that helps!