Move Issues to a new Sprint when a Sprint is Closed Edited

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?







0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,725 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you