Script Listener and Post Function unable to update another issue's Summary or FixVersions properties


Within the Script Listener or Post Function, we're referencing an issue's linked issues as MutableIssues and attempting to set the property (Summary and FixVersions) of those issues with the setSummary and setFixVersions methods. The end result is that the values are not changed. We are able to set the values of the originating event.issue or issue, but none of the linked issues properties. Example code below:

JIRA: 7.0.5


// Determine if this is an Epic, if so, return the Epic Link name
if (issue.getIssueType().name == "Epic") {
   // Variables for the issue itself
    IssueLinkTypeManager issueLinkTypeManager = ComponentAccessor.getComponent(IssueLinkTypeManager)
    IssueLinkManager issueLinkManager = ComponentAccessor.issueLinkManager
    Collection<IssueLinkType> storyLinkTypes = issueLinkTypeManager.getIssueLinkTypesByName('Epic-Story Link')
    Long storyLinkTypeId = storyLinkTypes[0].id
    // Defining Link Manager
    def optionsManager = ComponentAccessor.getOptionsManager()
    def issueManager = ComponentAccessor.getIssueManager()
    def fixVersion = issue.getFixVersions()
    // If the link type is Epic-Story Link
    if (storyLinkTypes) {
        // Iterating through all Links pertaining to Epic
        for (IssueLink link in issueLinkManager.getOutwardLinks( {
            // Checking the Epic-Story Link
            if (storyLinkTypeId ==
                  def linkedIssueStatus = link.destinationObject.getStatus().getName()
                MutableIssue linkedIssue = issueManager.getIssueObject(link.destinationObject.getId())
                linkedIssue.setSummary("New Summary")


1 answer

0 votes

Your script should look like the following:

import com.atlassian.jira.component.ComponentAccessor

if (issue.getIssueType().name == "Epic") {

    def issueLinkTypeManager = ComponentAccessor.getComponent(IssueLinkTypeManager)
    def issueLinkManager = ComponentAccessor.getIssueLinkManager()
    def issueService = ComponentAccessor.getIssueService()

    def storyLinkTypes = issueLinkTypeManager.getIssueLinkTypesByName('Epic-Story Link')
    def storyLinkTypeId = storyLinkTypes[0].id

    def user = ComponentAccessor.getJiraAuthenticationContext().loggedInUser
    // If the link type is Epic-Story Link
    if (storyLinkTypes) {

        issueLinkManager.getOutwardLinks( { link ->
            if (storyLinkTypeId == {
                def linkedIssue = link.destinationObject

                def updateParameters = issueService.newIssueInputParameters()
                updateParameters.setSummary("New Summary")

                def validationResult = issueService.validateUpdate(user,, updateParameters)

                if (validationResult.isValid()) {
                    issueService.update(user, validationResult)
                } else {
                    log.warn validationResult.errorCollection.errors

This uses IssueService to do the update for you for each of the linked issues which will save them in the database and reindex them.

Otherwise the post-function will only update and reindex the current issue that is being transitioned.

Hope this helps.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,965 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot