transition cards between next-gen projects

Dmitri_3xxaf3

We were going to create a new classic project with two boards and now considering to do it in next-gen projects instead. But here are three questions we not sure how to do:

New set up with next-gen projects

Product Project

Roadmap -> TODO -> in progress -> ... -> ready to build (done) 

Dev Project

backlog -> TODO -> in progress -> ... -> done

 

Questions

1. if we have a user story in Product Project can the user story automatically be moved into Dev Project when it reaches ready to build (done) ?

2. we noticed that moving the card manually from  ready to build (done)  to backlog does not clear resolved flag of the card

3. if the card is part of the epic in Product Project can it somehow retain relation to an equivalent epic in Dev Project

4. what is the best way to keep the same epic across those two projects?

Earl McCutcheon

Hi Dmitri,

First this is something that is not possible in jira natively with either Next-Gen or Classic project types, and would require an add-on to automate the move to a new project. 

Any add-on apps that would be able to do this are based on modifying the workflow of the project to trigger a custom post function, Some examples on this can be seen in this post.  Additionally, when it comes to modifying the workflow this is something that can only be done in a classic project and is not avaliable for next-gen.

Workflow customization isn't available yet for Next-Gen projects. It is on the longer term roadmap though. You can take a look at the recently shipped and coming-soon features of Next-Gen projects here. With additional notes about next-gen workflows is on this Community post by one of our product managers discussing the feature.  And the Features implementation is being tracked at the following request, make sure to add a vote to the request and add yourself as a watcher if you want notifications on the progress:

• https://jira.atlassian.com/browse/JSWCLOUD-17434

So to trigger the move action as you described you would want to look into various apps to trigger the move operation as described in the post linked above, but an alternate approach you can take that does not require any add-ons would be to have a single classic project with the full workflow for both the Roadmap and Development teams to work off of but rather than having them both work on the same board create a independent board for each team where the last status of the roadmapping team board is the first status of the Dev teams board.  then for any of the tracking gadgets you are using replace any filter you are using to track a individual users work with a "(assignee = username or assignee was in username)" to see the issues worked on by a user in the split workflow rather than just issues that are still assigned to a single user.

Regards,
Earl