Using Jira Issue Link to set Parent in DevOps

Use Case
, , , ,
1

Originally asked by Howard Kenny on 26 November 2020 (original question)

In Jira, we use the Epic issue type for two ‘epic types’; Business Epics (project = EDI) and Software Epics (project != EDI). We use a link type of ‘Is SWD Epic for Business Epic’ to link them.

I have Exalate configured so that Business Epics (EDI) generate an Azure DevOps ‘Epic’ and Software Epics (non-EDI) generate an Azure DevOps ‘Feature’ which is great. However, I’d ideally like to have the parent/child relationship between the Epic and Feature in DevOps - Business Epic being the parent.

2

Answer by Juan Grases on 26 November 2020

Outgoing on Jira

replica.issueLinks = issue.issueLinks

Incoming Azure:

def remoteLinkedIssue = replica.issueLinks.find{it.linkName == "The right link name"}?.otherIssueId
if(remoteLinkedIssue){
    issue.parentId = syncHelper.getLocalIssueKeyFromRemoteId(remoteLinkedIssue, "issue")?.id
}
3

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.