Howard Kenny
JSD and Jira Software are both on different instances?
Well, they're on the same server. Is that still classed as Local? I thought Local meant JSD > JSD, or Jira > Jira.
Local is on the same instance.
In Jira - Service Desk project and Software projects are projects with a different layout and functionality - but in the end they are all local issues.
Do you have sufficient info?
Indeed I do. Thanks for clarifying 'local'.
Francis Martens (Exalate) I lied. The documentation appears to be out of date, as it references LinkIssuesLocalSync.groovy (which we have in our external scripts library), but when using this in our Exalate script and error is thrown stating the script needs updating.
The script LinkIssuesLocalSync.groovy isn't in your listing though: https://docs.idalko.com/exalate/display/ED/External+scripts+library
I did wonder whether we needed to use https://docs.idalko.com/exalate/display/ED/IssueLinks.groovy?
The external scripts provided in the documentation are example implementations and are not necessary maintained.
Can you reiterate what you would like to have implemented?
The intention was to have a standard Jira link whenever issues are synced using Exalate, so we can then run reports in Jira looking for any linked issues (Exalated or other) using issueFunction. However, we now realise that this won't actually work because a report in Jira Software won't return issues in JSD (obviously!). Therefore, this might not be needed, but I guess it would be useful for other people in future looking to report in this way when issues are exalated in the same system.
This guide covers the creation of an epic link when it is a local connection. What should I do if the connection is between Jira Service Desk and Jira Software?
https://docs.idalko.com/exalate/display/ED/Jira+Server%3A+Creating+a+Jira+link+between+issues+in+local+sync