Automation that replicates status change in one software project board to another board?

[Ashley Leger]

Situation: same exact story in separate software project boards. 

Know you can link different stories to each other within Jira. 

Ask: is it possible to automate when the status changes in one software project board, that it automatically updates the same status in the other software project board? If so, how? 

Thank you in advance! 

[Nic Brough -Adaptavist- · Accepted solution]

> same exact story in separate software project boards

Do you mean it is the same story?  I.e. the same key?

[Ashley Leger]

Thank you for your response @Nic Brough -Adaptavist- , really appreciate it. 

Situation where we are creating a duplicate board for different companies. So all of the stories will be the same, but each company is tracking their status separately (i.e. the separate boards). 

We have another team that wants to track those statuses across all of the companies' boards, but within 1 of their own boards so that they don't have to jump from board to board. 

Know it's not an ideal situation, so trying to figure out how best to achieve their desired outcome. 

[Nic Brough -Adaptavist-]

Hmm.  "So all of the stories will be the same, but each company is tracking their status separately" doesn't really answer the question of whether the issues are the same story or different ones, so I still can't really answer the question.

But you've given us enough to work with to explain it.

The short version is that boards are not containers for issues, they are a view of a selection of issues. 

You can easily create your two boards, one for each team (as an aside, there is a very strong argument for considering "board = team"), and you can select the same issues on each board, so that both teams can work with the same issues.   But, because it is the same issue, if one team makes a change to an issue (edit, transition to new status), then that change will be reflected in the other team's board.

[Jorge Martinez · Accepted solution]

Maybe could be easier if you try to configure your views and filters in order to make visible the same issue in both projects instead of replicate.

But if that doesn´t work for you I think you could use a ScripRunner listener to do that. Configure the listener to trigger when issues are updated and prepare and script to identify related issues (maybe with specific link type), get their ID's and then execute the transition over them.