Populating Linked Issues In Email Templates.

Question

Question about getting the values for Linked issues into an email template post function. I've tried a number of ways to populate this via a script (in the condition section) of a send email post function. The script gives me the correct output in the script console but trying to get this out and into an email template is driving me NULL nuts. Here's a piece of my script. List allOutIssueLink = ComponentAccessor.getIssueLinkManager().getOutwardLinks(issue.getId()); for (Iterator outIterator = allOutIssueLink.iterator(); outIterator.hasNext();) { IssueLink issueLink = (IssueLink) outIterator.next(); def linkedIssue = issueLink.getDestinationObject() config.linkedIssue1 = linkedIssue.getKey(linkedIssue) String config.type = linkedIssue.getIssueType().getName(); String config.Outwardresults = linkedIssue.getIssueType().getName() + " " + linkedIssue.getKey() + " " + linkedIssue.getSummary() + "
" // returns null works in console config.outsnow = linkedIssue.getKey() // returns null config.typer = ComponentAccessor.getIssueLinkManager().getOutwardLinks(issue.getID()) //linkedIssue.getKey() // returns null config.putAll() return true Any help would be appreciated. I've probably spent too much time looking at this now and need to walk away for a bit. Again though any help would be appreciated. Thanks -CN

Craig Nodwell_7eve9b · Accepted Answer

Well I found the answer myself :) Here's my code: //Email Condition import com.atlassian.jira.issue.link.RemoteIssueLinkManager import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.IssueManager import com.atlassian.applinks.api.application.jira.JiraApplicationType import com.atlassian.jira.user.ApplicationUser import com.atlassian.jira.issue.Issue import com.atlassian.jira.user.ApplicationUser import com.opensymphony.workflow.loader.ActionDescriptor import groovy.xml.MarkupBuilder import com.atlassian.jira.config.properties.APKeys import com.atlassian.jira.issue.link.LinkCollectionImpl; import com.atlassian.jira.issue.link.IssueLink; // Get the components def issueManager = ComponentAccessor.issueManager def issueLinkManager = ComponentAccessor.issueLinkManager def remoteIssueLinkManager = ComponentAccessor.getComponent(RemoteIssueLinkManager) // Get the issue links to other issues def issueLinks = issueLinkManager.getOutwardLinks(issue.id) // Collect the HTML links pointing to the linked issues def baseUrl = ComponentAccessor.applicationProperties.getString(APKeys.JIRA_BASEURL) def linkedIssuesHtmlLinks = issueLinks.collect { issueLink -> def issueUrl = "${baseUrl}/${issueLink.destinationObject.key}" "This issue ${issueLink.issueLinkType.name} ${issueLink.destinationObject.issueType.name} ${issueLink.destinationObject.key} ${issueLink.destinationObject.summary} " } // Collect the HTML links pointing to the remote links def remoteLinks = remoteIssueLinkManager.getRemoteIssueLinksForIssue(issue) def remoteLinksHtml = remoteLinks.collect { remoteLink -> "${remoteLink.title}" } def outputs = " " //config.outputs allows us to pass the variables to the mail template // Display the links config.outputs ="""

Issue links:

${linkedIssuesHtmlLinks.collect { "* ${it} " }.join(' ')}

Remote links:

${remoteLinksHtml.collect { "* ${it} " }.join(' ')} """ return true ///////////////////////// Email Template

The $issue.issueType.name $issue.key has been assigned to you for approval.

Description:

${issue.description.replaceAll('h3.',"

").replaceAll("\*","

")}

System(s) Affected:

<% out << issue.getCustomFieldValue(com.atlassian.jira.component.ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("DevOps Systems"))%>

Requirements:

<% out << issue.getCustomFieldValue(com.atlassian.jira.component.ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("Requirements"))%>

Links:

${config.outputs}

${getWorkflowButtons.call()}