How to sync ticket transitions between Main and Sub Boards in Jira?

[Assad Rajab]

Problem Statement:

I have two Jira boards:

• Main Board
• Sub Board

The workflow for both boards is the same:

• To Do → In Progress → Done

Process:

1. A ticket is created on the Main Board.
2. The ticket is automatically cloned to the Sub Board and linked to the original ticket (all automated).

Requirement:

I want to automate the process such that when a ticket is moved on the Main Board (e.g., from To Do to In Progress), it should also automatically move to the corresponding status on the Sub Board.
This means if I transition the ticket on the Main Board, the cloned ticket on the Sub Board should be transitioned as well.

[Tomislav Tobijas · Accepted solution]

Hi @Assad Rajab ,

To start - are we talking about Jira or Jira Service Management? When talking about boards, are they separate or in the same projects?

As for automation, it is probably fairly simple. Use something like:

• Trigger: Issue transitioned
• Branch: Linked issues (check and do action on each linked issue)
• Action: Transition issue (transition status on linked issue)

That's assuming you have specific links between a ticket in the 'Main Board' and then one in 'Sub Board' (e.g. "clones" or "is cloned by").

Hope this helps.

Cheers,
Tobi

[Assad Rajab]

Hi Tobi, Thank you for the Answer, i am currently using Jira, I am not sure if it is the best solution for my use case.

[Clara Belin-Brosseau_Elements]

Hi @Assad Rajab

If you’re trying to sync statuses between two issues, I can suggest trying our app Elements Copy & Sync. It allows you to clone issues with all their content (summary, description, custom fields, comments, attachments, etc) and to synchronize any field or workflow across projects.

Could this be a solution for your use case?

The app is for free during 30 days (and it stays free under 10 users).

[Walter Buggenhout]

Hi @Assad Rajab,

Could you provide a little more context about your use case? Why do you duplicate tickets like this and make them act as if they are one and the same work item?

The automation rule in itself does not have to be complicated:

  trigger: issue transitioned (from to do to in progress)

  condition: issue fields / project = your source project

  branch: linked issues (specify the type of link you defined between the issues)

  action: transition issue (apply the same transition)

Just wondering why you can't / don't simply let users track the original issue instead of duplicating it?

Hope this helps!

[Assad Rajab]

Well, I work with multiple companies that send me Jobs, I want to be able to provide them with more information's about their tickets without having me switching between multiple boards all the time.
The idea was to have all my tickets in one Board(main) and on Ticket creation clone the ticket to the corresponding Board for the company (sub board/s).

The outside companies should not be able to see each others tickets, therefore the Sub Boards. 

In addition, the main Board will have longer Workflow than the sub boards.
Example:
Main Board: To Do → In Progress → Invoicing → Done
Sub Board: To Do → In Progress → Done