nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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 :

Screen Shot 2022-03-02 at 19.41.56.png

FYI, the ticket in MIB board has the linked issue (to BSM) with "blocks" type :
Screen Shot 2022-03-02 at 19.44.06.png

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:
Screen Shot 2022-03-02 at 19.46.49.png

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

Accepted answers

Pramodh M

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

Trudy P Claspill

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.

Screen Shot 2022-03-02 at 5.05.25 AM.png

Screen Shot 2022-03-02 at 5.02.20 AM.png

All comments

Pramodh M

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

Trudy P Claspill

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?

Screen Shot 2022-03-02 at 5.05.25 AM.png

Screen Shot 2022-03-02 at 5.02.20 AM.png

dwike_aprilia

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

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?

dwike_aprilia

yes and it works!

Trudy P Claspill

Right, you've got it.

Patrícia Gomes_50nvzu

Hi, @dwike_aprilia @Trudy P 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

Captura de ecrã 2022-03-11, às 16.21.28.png

Trudy P 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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

jira-service-management