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; } } }

bidirection update from JSM to JIRA Tickets

Ross Heatley

Hi all,

The workflow I'm trying to create is:

Ticket created in JSM board --> linked ticket created in Jira software board. When status of ticket is updated in Jira, update the ticket in JSM with the same status.

I have managed to create the automation to create the new ticket in the Jira board and link the two, but I can't get the updates firing. I've looked at several articles but none of them quite touching on what I need to do or are more in depth than I need.

Any help is much appreciated!

Accepted answers

Marc -Devoteam-

Hi @Ross Heatley

Welcome to the community.

You need multiple rules, but you can create rule as follows.

The rules needs to have the scope of both projects.

Trigger -> issue transitioned from status A to status B on the software project
Condition for linked issues, to check if there are linked issues
Branch rule, based on Linked issues
Edit action Transition to status that you require

Christopher Yen

Hi @Ross Heatley

Here's an example automation in one of my projects where we are syncing the statuses from two projects, but in my case the two projects use different statuses so we are mapping them, but hopefully this can serve as a reference for you to build yours. Let me know if you have any questions.

New Project (1).png

All comments

Marc -Devoteam-

Hi @Ross Heatley

Welcome to the community.

You need multiple rules, but you can create rule as follows.

The rules needs to have the scope of both projects.

Trigger -> issue transitioned from status A to status B on the software project
Condition for linked issues, to check if there are linked issues
Branch rule, based on Linked issues
Edit action Transition to status that you require

Christopher Yen

Hi @Ross Heatley

New Project (1).png

Clara Belin-Brosseau_Elevatic

Hello @Ross Heatley

As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone the Jira issue, link them together and then sync their status (both ways).

The configuration is super simple, you can check the guide here.

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

Ross Heatley

This is really helpful, thank you. As time has gone on, we're now trying to map the different statuses as well!

Ross Heatley

Thanks Marc. This has been super helpful.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management