How do I set up an automation to transition an issue from a Jira Project to the linked issue in JSM?
Asked by Shayden Frankhouser:

Hello!

I'm looking to set up an automation between a Jira Service Management (JSM) project, and a Jira project (JP).

JSM - when a request is submitted, I would like to triage the request for completeness. When the request is ready for work, I have an automation created to send it to our JP board.

I also have an automation created, so that when the automation runs to the JP board, it also creates a linked issue (relates to) which is the JSM issue.

Both issue types are "tasks" and both "tasks" use the same workflow.

JP - when the request is being worked on in the JP (its a kanban card), I want the linked issue from JSM to also be updated when the kanban card is updated. i.e., when the JP issue transitions to "Assigned" I want the JSM request to also transition to "assigned"

How do I do this?

I've tried Look up tables, linked issue types, issue type = "task", etc.

I thought I read somewhere on the Atlassian community that they may need to be different issue types, but my Atlassian PO said that was not true, so now I'm stuck.

TYIA!


Answers:
author: Clara Belin-Brosseau
body: Hello [@Shayden Frankhouser](/t5/user/viewprofilepage/user-id/5525502)

If you're seeking for an easier way **to clone an issue from JSM to a Jira project and keep their workflows in sync** , you can try [our app Elements Copy \& Sync](https://marketplace.atlassian.com/apps/1211111/elements-copy-sync-clone-jira-issues?tab=overview&hosting=cloud?&utm_source=community&utm_medium=answer&utm_campaign=question_2732574&utm_keyword=CS&utm_vendorID=4952) that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You can check our guide [here](https://doc.elements-apps.com/copy-and-sync-jira-cloud/synchronise-the-status-of-two-jira-issues?&utm_source=community&utm_medium=answer&utm_campaign=question_2732574&utm_keyword=CS&utm_vendorID=4952).

You can try the app for **free during 30 days** (and it stays free under 10 users).

Kind regards,

Clara


author: Walter Buggenhout
body: Hi [@Shayden Frankhouser](/t5/user/viewprofilepage/user-id/5525502) and welcome to the Community!

At the core, you basically need an automation rule that looks like this:

![Screenshot 2024-06-20 at 20.56.34.png](https://community.atlassian.com/t5/image/serverpage/image-id/330938i3661952BD65BD85B/image-size/large?v=v2&px=999 "Screenshot 2024-06-20 at 20.56.34.png")

Because you are working across 2 different projects, you may need to make sure to include both projects in the scope of your automation rule (you can do so on the *Rule details* page). And also pay attention to the direction of the link between your issues (relates to may have an *is related to* counterpart representing the opposite end of the link.

If your issues are indeed sharing the same workflow, you could also choose to *copy* the transition *from the trigger issue*. That would make your automation rule more dynamic then when you explicitly select status names. You can add additional conditions to validate if your linked issues are in a certain status, etc. But from the above starting point, you should have all you need to get going.

Hope this helps!

comments: author: Shayden Frankhouser
body: Hi Walter, thank you for the fast response!

This is how I have it set up:

When I triage the request, I want to change the status to "Ready for Legal Review" - this creates a linked issue with the linked issue type "relates to" and a "task" in the JP kanban in the column "ready for legal review".

Problem: When this automation kicks in, it creates the task, and creates the linked issue type, but pushes it back to the first status in the workflow "Ready for review"

Here are my automations:  

<br />

![2024-06-21_07-27-55.png](https://community.atlassian.com/t5/image/serverpage/image-id/331111i9A990169DF5B42CE/image-size/large?v=v2&px=999 "2024-06-21_07-27-55.png")

I'm also unable to add additional projects to my "scope".

![2024-06-20_16-51-34.png](https://community.atlassian.com/t5/image/serverpage/image-id/331112i55EE4558E299E478/image-size/large?v=v2&px=999 "2024-06-20_16-51-34.png")

![2024-06-21_07-33-56.png](https://community.atlassian.com/t5/image/serverpage/image-id/331114iDECFD34D3C474ED5/image-size/large?v=v2&px=999 "2024-06-21_07-33-56.png")


Tags: cloud

jira-service-management

jira-service-management-cloud