what to do with issues that do not get deployed after a sprint is closed

[Shari Fitz-Patrick]

WE do not always deploy issues at the end of each sprint.  They might only get deployed a couple of months later. If we keep them in the sprint they affect Velocity reporting.  I was thinking of using a Kanban board for deployments.  We would put the issue into Done status once the product owner review has taken place.  We would then move from Done to the kanban board into the Deployments status.  Do you think this would work?

[Mark Segall]

Hi @Shari Fitz-Patrick - I would recommend taking a closer look at leveraging releases...

Every deployment should be captured in Jira as a release and stories should reflect their release by way of the fixversion field.  This way, issues can be resolved in their current sprint without getting lost into a black hole.  When it comes time for deployment, the Jira release becomes your source of truth and is indiscriminate of what sprint each story was completed.  There are plenty of native reports to provide visibility into the release.