Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Listener not updating fields on transition screen

Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 04, 2019

I have a parent issue and a sub-task which both share a screen. I have created a custom listener which updates the fields when it is edited on the edit screen, but it does not work when it is updated on the transition screen. The listener listens to the 'Issue Updated' event, and I have configured the workflow transition post functions so that this event is fired here.

I read somewhere that this may be an event problem, but I am not sure what I am doing wrong. The code is as below:

import com.atlassian.jira.event.issue.IssueEvent
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption

def customFieldManager = ComponentAccessor.getCustomFieldManager()
def issueManager = ComponentAccessor.getIssueManager()
def changeHistoryManager= ComponentAccessor.getChangeHistoryManager()
def user = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
def issue = event.getIssue()

if( == "Joiner Information" || == "Leaver Information"){
//get the parent issue
def parentIssue = issue.parentObject
//get all the custom fields
def customFields = customFieldManager.getCustomFieldObjects(issue)

//get the changed item list from change log
def changeLogs = event.getChangeLog()
def changedItem = changeHistoryManager.getAllChangeItems(issue).findAll { it.changeGroupId ==}

//mutating parent issue
def mutableParentIssue = issueManager.getIssueObject(
//update parent issue if the changed item is a custom field
changedItem.each { item ->;
if(customFields*.name.contains(item.field)) {
def customFieldName = item.field
def customField = customFieldManager.getCustomFieldObjectByName(customFieldName)
def customFieldValue = issue.getCustomFieldValue(customField)
mutableParentIssue.setCustomFieldValue(customField, customFieldValue)
//updating the parent issue only if condition is true
issueManager.updateIssue(user, mutableParentIssue, EventDispatchOption.ISSUE_UPDATED, false);

I get the following error:


2019-02-04 13:18:28,739 ERROR [runner.AbstractScriptListener]: *************************************************************************************
2019-02-04 13:18:28,739 ERROR [runner.AbstractScriptListener]: Script function failed on event: com.atlassian.jira.event.issue.IssueEvent, file: <inline script>
java.lang.NullPointerException: Cannot get property 'id' on null object
	at com.onresolve.scriptrunner.runner.ScriptRunnerImpl.runScriptAndGetContext(ScriptRunnerImpl.groovy:173)
	at com.onresolve.scriptrunner.runner.ScriptRunner$runScriptAndGetContext$2.callCurrent(Unknown Source)
	at com.onresolve.scriptrunner.runner.ScriptRunnerImpl.runStringAsScript(ScriptRunnerImpl.groovy:162)
	at com.onresolve.scriptrunner.runner.ScriptRunner$runStringAsScript$ Source)
	at com.onresolve.scriptrunner.canned.jira.workflow.listeners.CustomListener.doScript(CustomListener.groovy:123)


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events