Cloning Jira board/ticket - one the original ticket stays and a clone ticket moves to another board

Question

Hi Everyone, I have an interesting request. Is it possible to a clone board/ticket because the original ticket on board X moves to a different board either A or B depending on the teams who is going to work on it. However, because the ticket on board X dissappears, the view of all the tickets some not started some in progress some closed is no longer possible to see. So, how does one resolve such a problem where I get to see all the tickets progress on one board/one view all automated without me creating a new board and tickets manually to track them?

ThankYOU

Puru

Clara Belin-Brosseau_Elevatic · Answer

Hi @Puru

If you want each team to work on their own issue while maintaining a master view automatically, you can use our app Elements Copy & Sync.It lets you:

Automatically clone issues when moved or transitioned.

Sync statuses, comments, or fields between the original and the clone.

Keep a single “overview” issue or board that always shows up-to-date progress across teams.

Here’s how it could work:

When an issue is moved from Board X to Board A or B, Elements Copy & Sync creates a linked copy for that team.

Progress updates stay synchronized, so your Board X can display the overall picture without manual duplication.

Don't hesitate to try the app for free

Gor Greyan · Answer

Hi @Puru

Welcome to the Atlassian Community!

In Jira, boards are just views based in filters(JQL).
That means a ticket only "disappears" from Board X because its JQL filter no longer matches after you move it.
You don't need to clone or duplicate tickets - you just need a shared filter that covers all board.

Go to Filters -- > Create Filter
Write JQL, that includes all relevant projects, boards.
For Example.
Project in(X,A,B) order by updated desc

Then
Go to Boards --> Create Board --> From existing filter, and choose that filter.

After all, you will have a single Kanban or Scrum board that automatically shows every issue across all.

Jayesh Raghuvanshi · Answer

@Puru

You can try any of the below suggesstions:

* Create a unified filter using JQL* To aggregate tickets from multiple projects you can create a JQL taking below reference
project in ("Project X", "Project A", "Project B") ORDER BY Rank ASC

* Create the new board using the above filter

Below JQL can be used

Typical JQL Examples for Cross-Project Unified Views

All open issues in Projects X, A, B:
project in ("X", "A", "B") AND statusCategory != Done

All issues (any status) in Projects X, A, B:
project in ("X", "A", "B")

Issues by team/assignee:
project in ("X", "A", "B") AND assignee = <username>

Thanks
Jayesh R