How to replicate the status from one board to Jira Service Desk ticket through automation

[dwike_aprilia]

Hi all, again I have several problems with automation. 

Here is my case. So whenever the user creates the ticket from the Jira Service Desk, am cloning the ticket into another board (Let's say MIB board.)

So whenever the dev updates the status field (through MIB board), I would like this is gonna happen in the Jira service desk (BSM board) ticket as well. So, I create the rule (in project-level of MIB board) like below :

FYI, the ticket in MIB board has the linked issue (to BSM) with "blocks" type :

But, this rule doesn't work at all . When I update the status from MIB board, it only happens on MIB board.
here is the log:

Can someone help me? any ideas would be very helpful. Thanks!

[Trudy Claspill · Accepted solution]

Does the issue MIB-2591 have a "blocks" link to an issue in the BSM project?

If so, did you create this rule in the MIB project or as a Global Automation? 

I believe in order to be able to reference the two projects you will need to create a Global Automation and set the scope to both projects. Then you may need to make the rule more complex to ensure it is triggered by only the status changes in the MIB project, and changes only the linked issues that are in the BSM project.

[dwike_aprilia]

Hi, @Trudy Claspill it works! I follow your example above and now it works. Thanks for giving me help! :D

So basically if I want to update on one side and I want to that reflect in the other board as well, I need to make the rule a global rule, right?

[Trudy Claspill]

Right, you've got it.

[Pramodh M · Accepted solution]

Hi @dwike_aprilia 

If multiple projects issues are involved, you should properly scope the projects from the global automation section.

So to resolve this, create a global automation with same rule as above shown in the image and select both JSM project and Jira software project

Thanks

[dwike_aprilia]

yes and it works!

[Patrícia Gomes]

Hi, @dwike_aprilia @Trudy Claspill @Pramodh M 

I have the same problem, I replicated the rule you posted here, but dont work :( 
my TJ clone doesn't change to "done" when CLINEXGEN ticket changes to "done"

Could you help me?

Tks 

[Trudy Claspill]

@Patrícia Gomes 

Is your Rule a global rule scoped to include both projects? Notice in your image under Scope it says Multiple Projects and that can be modified in the Global Automation. Can you confirm both the projects are specified there for the rule scope?

Can you confirm that you have changed an issue to Done in your source project, and the issue has an "is cloned by" link to an issue in the other project? What does the audit log for the rule say when such an event occurs?

[Patrícia Gomes]

@Trudy Claspill

Thank you for your answer! 

Yes, I applied this rule to both projects,

I made recording of what I did so you can see better.

Create issue in TJ and Clone issue TJ to CLINEXTGEN: https://i.gyazo.com/1e0b0740d62d5193501ead11eb727f0d.mp4 

Change status CLINEXTGEN to Concluido: https://i.gyazo.com/fe9e811debfe5171071e1154e21a565b.mp4 and  https://i.gyazo.com/6e069113528e62069c2f664be415f742.mp4

nothing change on TJ clone :(

Tks for your help

[Trudy Claspill]

Can you click on the Audit Log option in the rule and expand the log entry for the event where you changed the source issue?

[Patrícia Gomes]

@Trudy Claspill 

this?

doesn't seem to work. It did not log after running the action :( 

[Trudy Claspill]

I think your problem is here:

I think if you change that from "clones" to "is cloned by" then your Automation should work.

[Patrícia Gomes]

@Trudy Claspill 

It is working!

Thanks for your help! :)