Using scriptrunner to clone an issue in another JIRA instance

Adolfo Casari
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 22, 2013

There is this scriptrunner example to clone an issue in Jira as a workflow postfunction:

https://jamieechlin.atlassian.net/wiki/display/GRV/Post+Functions#PostFunctions-Cloneissuewithdependencylink

Is it possible to adapt it to clone an issue in another Jira instance?

Thank you,

2 answers

1 accepted

0 votes
Answer accepted
Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 22, 2013

I may not be answering your question. But there is an alternative way in cloning issue to another JIRA instance, by using JIRA to JIRA Issue Copy. Install in both JIRA instance and get the Application Links running.

0 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 22, 2013

It would not be an adaptation, but something completely different using the rest api and the RemoteIssueLinkService.

However as Zulfadli says I would look to existing plugins as there may be some custom field matching to be done which, although not tricky, is probably time-consuming and boring work.

If that plugin only provides a web-item to do the remote copy, you can probably work out how to script it using script runner.

Suggest an answer

Log in or Sign up to answer