Migrating tickets between 2 next-gen boards

[Ashleigh Campbell]

We have 2 boards. We want to be able to move tickets from the backlog of our development board into the new release board as well as migrate completed tickets from the development board into the release board. Each time we attempt to do this, we are faced with losing all of the information in the ticket. Has anyone managed this successfully?

[Ravi Sagar _Sparxsys_]

Yes and also read this page for more details on this topic.

[John Funk]

Hi Ashleigh,

Since you are using Next-gen projects that is going to happen. Custom fields created in one Next-gen project cannot be carried over to other Next-gen projects. So data in those fields will be lost. 

If that's the kind of thing you want to do, I would suggest you use Classic Software projects to perform that function as they can use shared fields across those project types. 

[Bill Sheboy]

Hi @Ashleigh Campbell 

Yes, and to what John says...

When you move completed work issues from one board to another, those items would be re-opened and you lose visibility to the development teams completed list of work.  If your teams are completing this work rapidly, consider instead having one development and release board.  If instead the dev and release work happen on very different cadences, consider cloning completed dev items to move them as new items for release.

Best regards,

Bill