Correct way of updating an issue's field via a custom ScriptRunner listener and saving to DB?

Question

So here is the script. I omitted some code, but ideally this is how it is. My main issue is that when I run the "issueManager.updateIssue" function the issue's due date does not get updated. However in the history, it does say the change value was update.

Is this the proper to way to do this?

//manager to manage ineractions with issue

IssueManager issueManager = ComponentAccessor.issueManager

//user context of who is working on this ticket

ApplicationUser user = ComponentAccessor.getUserManager().getUserByKey("issuebot")

//the database view of an issue

Issue nonMutableIssue = event.getIssue()

MutableIssue mutableIssue = issueManager.getIssueObject(event.issue.getKey())

//print orignal dute date before change

//make the change

c.setTime(*SOME RANDOME TIME SET*)

String dateStr = (c.get(Calendar.MONTH) + 1) + "/" + c.get(Calendar.DAY_OF_MONTH) + "/" + c.get(Calendar.YEAR)

log.info TAG + "${mutableIssue.getKey()} due date set to: ${dateStr}"

mutableIssue.setDueDate(new Timestamp(c.getTimeInMillis()))

//updates the changes to the issue in the database
def updatedIssue = issueManager.updateIssue(user, mutableIssue, EventDispatchOption.ISSUE_UPDATED, false)

//run a reindex to get the latest changes made from the database
event.issue.reindex();

Hauke Bruno Wollentin_kh2tr0 · Answer

Wow, great catch. Than it's up to the plugin vendor I'd say :)

Abi_zs42ua · Answer

Thank you for taking the time and helping me out.

I looked more into the problem and discovered these two errors:

[o.c.g.runtime.m12n.MetaInfExtensionModule] Module [Innovalog Groovy extensions for JIRA] - Unable to load extension class [org.codehaus.groovy.runtime.SqlGroovyMethods]

[c.a.j.cache.request.RequestCacheRecorderImpl] Invalid use of RequestCache by thread: default-application-role-manager-cache-refresh.Incorrect usage of JIRA API.

After a little more research I found out that the plugin "JSU automation suite for jira workflows" is the reason why I could not update the fields to the database. Once I disabled the plugin, the fields were updated to the database. It seems like JSU is causing something to mess up when the issue gets created.

Hauke Bruno Wollentin_kh2tr0 · Answer

I used the base part of your code to reproduce this, but in our instance (Jira DC 9.9.1) this works:

The actual code:

import java.sql.Timestamp

import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.user.ApplicationUser
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.component.ComponentAccessor

def issueManager = ComponentAccessor.getIssueManager()

MutableIssue issue = event.getIssue() as MutableIssue

Timestamp newDueDate = Timestamp.valueOf("2023-10-23 10:10:10.0");

issue.setDueDate(newDueDate)

def user = Users.getLoggedInUser() as ApplicationUser

issueManager.updateIssue(user, issue, EventDispatchOption.ISSUE_UPDATED, false)

Does "the update don't go into the DB" mean, that in your issue view the due date field is incorrect and not set to the value that your listener should set?

Do you see any log lines in atlassian-jira.log about that?