How to transition the status of a bug in a project based off of a linked bug in another project.

[Colton Carnevale]

So I am managing a software team, and I want to create a second project for my support staff to create and track bugs. Let's call the software tracking project ST and the bug tracking project BT. Both projects have kanban boards which looks like the following:

BT Kanban board columns: 
1. Accepted
2. TO DO
3. IN PROGRESS
4. IN REVIEW
5. DONE 

ST Kanban board columns:
1. TO DO
2. IN PROGRESS
3. IN REVIEW
4. DONE

Currently, I have an automation set up to do the following: 

1. When: Issue Transitioned
    FROM To Do TO Accepted

2. Then: Create a new
     Bug IN ST

So in other words, when a bug in BT is moved from the backlog to the kanban board in the accepted column, I create a new bug in ST which is then placed in the backlog.

Goal:

Now the goal that I am trying to accomplish is for BT to listen and reflect the status of the bug in ST so the support staff can see an updated status of the bug as the dev team works on transitioning the bug through the development process.

This issue is that I cannot figure out a workflow to reflect the status of a bug from ST to BT. Any help would be appreciated. 

[Belto]

Assuming that the Bug in ST is being linked to the BT issue, you could use a  Branch rule in Automation for Jira which would allow you to pull information from linked issues

• Branch automation rules to perform actions on related issues

[Colton Carnevale]

Yes, the two issues are linked. The ST shows the issue in BT that it is cloned by. 

So what would the automation look like to cause changes in ST to update BT?

[Belto]

The rule would look somewhat like this