Issue Summary

At this moment, Jira admins are not stopped from creating a classic software board from a Next-gen project. As such, if the filter of this board contains several Next-gen projects, on the column mapping of this board, the Next-gen statuses will appear duplicated. This happens because Jira treats each Next-gen project as an individual entity.

The problem with this design is admins cannot differentiate which status belong to which Next-gen project.

Steps to Reproduce

1. Create multiple Next-gen projects;
2. Create a filter with those Next-gen projects;
3. Create a classic software board from this filter;
4. Access the column mapping of this board:

Expected Results

Statuses with the same name are shown only once.

Actual Results

Several statuses with the same name are shown, without differentiation on which Next-gen project they belong to.

Workaround

Admins can either remove the Next-gen projects from the filter used by the board or consider migrating their Next-gen project to classic ones.