Creating linked issues between JSD and Jira Software KANBAN boards.....

Question

We are using Jira Service Desk to receive issues/questions from customers and Software Kanban boards to allow teams to work through them.

I have managed to created the "linked issue" so that a Kanban card is created and linked to its respecitve Jira ticket - but the Kanban cards are blank.

I need the information supplied in the first ticket to be carried across to the Kanband card in full - what I am doing wrong?

Thanks in advance!

Ismael Jimoh · Answer

Sorry for the late reply.

If all you are interested in is the first part of the ticket then yes all the listed solutions work including the Scriptrunner option.

Similar to backbone which I mentioned in my last reply, you can also use Excalate which provides a very similar functionality and you can specify in each case to trigger the copy of information during the very first event. (Issue Created for Excalate or Backbone and Create issue transition post-function for Scriptrunner).

Hope this helps.

Regards.

Luke Bryant_gec52z · Answer

What I am aiming for and need is just when a ticket is created in Jira Service Desk, that a card creates in the linked Kanban (this happens now) BUT importantly, the information in the SD ticket is copied into the Kanban card.

I am not worried about further editing etc, just the first information.

Kristian Walker _Adaptavist_ · Answer

Hi Luke,

Thank you for your question.

I can confirm that the ScriptRunner for Jira Cloud plugin provides the Clone Issue workflow post function as described in the documentation page located here.

Using this post function you can clone an issue during a workflow transition in either the current project or to a different project and can specify the link type to use.

I can confirm that when cloning the issue that the custom fields and comments will be copied across as mentioned in the documentation page linked above.

Please note that this function only clones the issue as it was when the post function is run and does not sync any changes to the cloned issue when the issue it was cloned from is updated.

If this response has answered your question can you please mark it as accepted so that other users can see it is correct when searching for similar answers.

Regards,

Kristian