Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
5.1.8, 6.4.3, 6.4.10, 7.0.10, 7.1.2, 7.1.8, 7.3.0, 7.1.9, 7.6.2, 7.2.4
-
5.01
-
93
-
Severity 2 - Major
-
16
-
Description
Actual behavior:
When you import a project from Instance A into Instance B, if there's an Application Link cross linking issues, the Remote Links are not carried over.
Steps to reproduce:
Instance A has ATP-1 issue linking AWD-1 issue that belongs to Instance B. When importing the ATP project into Instance B, the link should be kept and updated to reflect to the correct place.
Expected behavior:
Have the remote links imported into the instance.
Workaround:
The API referenced is here:
This step will performed after the project has been imported in the target source:
https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-getRemoteIssueLinks
Basically we'd do a simple get from the source for all the issues in a project:
GET URLOFSOURCE/rest/api/2/issue/{issueIdOrKey}/remotelink
{
"id": 10001,
"self": "http://10.125.88.109:8080/jira730/rest/api/2/issue/KRIS-11/remotelink/10001",
"application": {},
"object": {
"url": "https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-getRemoteIssueLinks",
"title": "test",
"icon": {
"url16x16": "https://docs.atlassian.com/favicon.ico"
},
"status": {
"icon": {}
}
}
}
All you need to do is change the URL to the target instance and the call to a post, the JSON doesn't need to be reformated
POST /rest/api/2/issue/{issueIdOrKey}/remotelink
{
"id": 10001,
"self": "http://10.125.88.109:8080/jira730/rest/api/2/issue/KRIS-11/remotelink/10001",
"application": {},
"object": {
"url": "https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-getRemoteIssueLinks",
"title": "test",
"icon": {
"url16x16": "https://docs.atlassian.com/favicon.ico"
},
"status": {
"icon": {}
}
}
}
Attachments
Issue Links
- incorporates
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
-
JIM-1151 Loading...