How to surface Next Gen project tickets in a Classic dashboard; link Next Gen and Classic tix

[sckuhn]

We have a complex predominantly Classic implementation of JIRA with multiple teams and projects. One of our teams/projects is migrating over to Next Gen. When doing Scrum of Scrums or attempting to link between Next Gen project management ticketing and Classic development team tickets we are hitting a wall.

Is there a way to link Next Gen tickets or - at a minimum - view them in a Classic board?

[Earl McCutcheon · Accepted solution]

Hi Stephan,

This is not recommended, the Next-gen projects work on different field mapping's and configurations than the classic project types.  You can read more about the differences at "Classic and next-gen project templates in Jira Software Cloud".

If you edit your classic board filter to return issues from a Next-gen project and map the statuses in your board column, it should properly display the Next-gen issues in your board, However there are going to be conflicts in the data.  You will see status duplication from statuses in the next-gen projects as each next-gen project is going to have independent statuses with the same naming convention. 

In next-gen boards, you can't explicitly configure your workflow as you're used to in classic Jira projects. You modify the workflow by simply adding or rearranging the columns on your next-gen board.  Jira creates in the background a separate workflow for every project - and this is the reason why you have to map statuses for every next-gen project you want to add, duplicating the statuses for every project as there is no shared configurations.

The story points will have some variations in the mappings as in Classic projects, the estimation is measured on the Story Points field in Next-gen projects, the estimation is measured on the Story Point Estimate field, the classic board will not merge the story point estimate into the existing Story point and the entities are entirely separate per project type with no cross over, so you will not be able to report accurately between the two project types.  And using a Next-Gen project on a classic board you will run into this scenario.

Overall Next-gen projects are designed to be worked on from the next-gen board, and should not be added to the classic boards.

Regards,
Earl

[Maria Flores]

I have tested combining Next-gen and Classic projects in a single board and although I can create a filter which includes all projects, I cannot get the Next-gen issues to display in the board.

I have mapped the separate duplicate statuses into the columns I want them in, Jira accepts that but still doesn't show the NextGen issues in the combined board.

Has anyone been successful with this?

[Debby Lin]

We are using both but I think it was lack of understanding in the initial stage of using Jira. Now, I run into the same issue as we are trying maintain all the status quo of all projects created initially and running sprints in one main project. Unfortunately, I ran into the same issue as Maria. 

[Emily Chan]

Hi @sckuhn and @Maria Flores !

We're currently doing research on understanding more about organisations who are currently using both Classic and Next-gen project types at the same time. Would you help us learn more about you and your use cases?

A one-hour chat with you would be immensely helpful, and we’ll send you a $100 gift card as thanks. If you’re interested, please email me at echan@atlassian.com.