Project board that pulls issues from other project boards via labels

[Davina Legah]

Hi everyone, I am trying to create a new project board that will need to pull issues from other existing project boards that have a specific label.

For example, if a new issue is added to an existing project board and is labelled with that specific label, it will create a copy of that issue in the new project board. 

The new project board will only contain issues with that specific label. 

[Trudy Claspill]

Hello @Davina Legah 

Welcome to the Atlassian community.

Please clarify this statement:

it will create a copy of that issue in the new project board

Issues are contained in Jira Projects. An issue exists in only one Jira Project at a time.

A board is just a method to visualize issues. Boards select the issues to show based on a filter. Any given issue can display in multiple boards at the same time, because any given issue can match the criteria of multiple filters. Any change made to that one issue in any board where it displays will be reflected in all boards where it displays, because it is the same issue in all boards.

So, do you really want a separate copy of the issue in a different Jira Project, or do you just want to see the same issue in multiple boards?

[Jakub Cieslak]

Hi there! If you want to list those items in your custom board, that's simple:

1. Open your custom Board, find the 3 dots on the right, select "Configure board".
   
2. Navigate to "General" on the left, and adjust "Board filter" accordingly (e.g., specify which project(s) should be included, what label(s) and so on).
   

However, if you really want to duplicate those items and have them replicated in another Jira project, you could utilize global Jira Automation. But! This is not recommended, because those automation calls are not free after a certain monthly threshold, and you have a big risk that the data of the original ticket and the duplicated one will be out-of-sync.

Sure, there are some ways to keep those two tickets in sync, but this is very expensive (resource wise), and not worth it, in my opinion. There were some use-cases in my past that this made sense and I went this "duplicate ticket" way, but in most cases, you really do not want to do that.