Move Issues to a new Sprint when a Sprint is Closed

Chris Kibbey October 23, 2017

We've had a requirement for the following:

'It is suggested that the last column on the board is Signed Off. This would, in effect, be Done as far as the team are concerned and this is the point at which work would count towards the team’s velocity. When a sprint is closed, any tickets in this column would not move on to the next sprint as hangover.

Instead, they would automatically move to a new board so that they are still visible and trackable by the relevant parties e.g. Tech Leads, Project Managers, Release Manager etc.

This would give visibility as to which work items had been released to which environments.

Some types of ticket may only be released to certain environments and this would need to be catered for in the workflow.

This board could be fed from multiple projects and teams.'

Given that Projects and NOT Boards contain Issues, would this be possible by creating a Workflow with a set of Custom Resolutions which could then be pulled into a new Sprint via a filter?

 

 

 

 

 

 

1 answer

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 22, 2021

Hi @Chris Kibbey 

Can you please clarify what exactly you want to do, because it's not that clear.

Suggest an answer

Log in or Sign up to answer