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 automatically create linked issues in Jira SW on a request status change in servicedesk

Devops_nx9hv7

Hi,

We have a Jira software self hosted server instance for our R&D department and recently we have a servicedesk self hosted instance for the customer support department.

Manually I can create issues in jira and link them with SD requests. I want to automated this proces on a state change of the request in SD. When linked, I want the request to be in sync with the linked issue. On certain status changes of the linked issue in jira software, the SD request should change to another state automatically.

I've read an article on how to do that ( (https://confluence.atlassian.com/servicedeskcloud/blog/2017/12/automatically-create-linked-issues-from-new-requests?_ga=2.172263072.2008128397.1578472736-103221097.1549351740).

But unfortunately this does not work for me. Does this functionality is not provided in the server version?

I've tried other add-ons; scriptrunner and automation for jira. I can create linked issue in a SD project but not in a Jira software project.

What is the problem?

Kind regards,

Frank

Accepted answers

All comments

Jack Brickey

What exactly isn’t working? Aside from the syncing of transitions are you able to do a basic automation to create a linked issue? If you can do this manually you certainly you should be able to automate with built in (some limitations) and certainly with A4J and Scriptrunner. Please provide details of what you have tried and the results. Let’s start with built in and see if we can get the basic case working.

Julie d_Antin _Elements__bsgnak

Hi @Devops

Take a look at Elements Copy & Sync, which allows you to automate the creation of linked issues.

You won't be able to move the linked issues through a workflow (changing the status), but the app will meet your need to create issues in Jira Software or Core, or even in remote Jira instances.

Jack Brickey

@Julie d_Antin _Elements_ ,

but why would this work where the others would not? I think we need to understand Devops requirements and roadblocks before recommending another addon. The thing that strikes me here is that they have not been successful with 3 capable methods so I have to wonder if something else is goin on here.

Devops_nx9hv7

In SD; Project settings->Automation. There is no "create issue" in the action dropdown. See screenshot.

Jack Brickey

Keeping my comments in this thread...

so I guess that server is different as I see this ...

so let’s cast the OOTB aside for the moment and check A4J assuming it is still installed.

Devops_nx9hv7

Another try was with Scriptrunner. I tried to clone and link via an post function on a workflow transition. Under target Project drop-down I get only the SD projects not the Jira software projects. So I cannot clone the SD request into a Jira software issue.