I tried your script as is (only changed the field names) and it worked (using Jira 7.13.2).
So it may be down to the type of fields.
But I do see something unnecessary:
This:
def tgtField = customFieldManager.getCustomFieldObjects(event.issue).find {it.name == "Risk Score"} Could be simplified (and use the same pattern as the other field):
def tgtField = customFieldManager.getCustomFieldObjectByName("Risk Score")Then, you can split up that last line so that you get a clearer indication of where the issue is coming from (though the error message is pretty clear).
def oldValue = issue.getCustomFieldValue(tgtField)
log.info "Old Value for 'Risk Score' was $oldValue"
//only attempt to update the target field if the new value is actually different
if(oldValue != EpicRiskScoreValue){
def modifiedValue = new ModifiedValue(oldValue,EpicRiskScoreValue)
tgtField.updateValue(null, issue, modifiedValue,changeHolder)
//you may want the ticket history to show that change, in that case you need to log it yourself
// requires import com.atlassian.jira.issue.history.ChangeLogUtils
def currentAppUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
ChangeLogUtils.createChangeGroup(curretnAppUser, issue, issue, changeHolder.getChangeItems(), false);
//Also, the above will not update the index for the issue, you must also do that yourself
// Requires
// import com.atlassian.jira.util.ImportUtils
// import com.atlassian.jira.issue.index.IssueIndexingService
ImportUtils.setIndexIssues(true)
ComponentAccessor.getComponent(IssueIndexingService.class).reIndex(issue)
ImportUtils.setIndexIssues(false)
}
You should be able to get a closer clue of what's wrong with your script. Look at what "oldValue" is or if you still get an error on getCustomFieldValue(tgtField)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.