Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Scriptrunner scripted fields integration with Tempo fails

Performing the same script via the Script Console works but via the Scripted Field it fails to retrieve Tempo data like worklog attributes. Are these maybe not saved yet? How to deal with this?

Listening for the event Work Logged on Issue

def attribute = workAttributeService.getWorkAttributeByKey("_Account_").returnedValue
return workAttributeValueService.getWorkAttributeValueByWorklogAndWorkAttribute(,

"returnedValue" is empty during a scripted field execution, it works fine via the Script Console.

2 answers


Could you please provide full source code for your listener?

You can perform following steps:

1) Check out this topic

2) Add, log.error etc. to you code in order to get info from logs.

Skipping some code but this should help. Like mentioned, retrieving this via the script console, by taking one of the last worklogs, works but via this listener it's null


import com.onresolve.scriptrunner.runner.customisers.PluginModule
import com.onresolve.scriptrunner.runner.customisers.WithPlugin
import com.tempoplugin.core.workattribute.api.WorkAttributeService
import com.tempoplugin.core.workattribute.api.WorkAttributeValueService


WorkAttributeService workAttributeService

WorkAttributeValueService workAttributeValueService

def issue = event.issue
def workLogs = worklogManager.getByIssue(issue)
def latestWorkLog = workLogs.sort {}.last()
def timeSpent = latestWorkLog.getTimeSpent()

def attribute = workAttributeService.getWorkAttributeByKey("_Account_").returnedValue // Account
log.error attribute
def accountValue = workAttributeValueService.getWorkAttributeValueByWorklogAndWorkAttribute(,
log.error("Ret value ==== " + accountValue.returnedValue)

Hi. Did you ever solve this issue? I'm also trying to use a scripted field to get the Tempo Account Category as an issue value. Like you described in preview it works fine, but in JQL and filter gadgets the returned value is null.

No.. Tempo fills the value after this event. Maybe they’ll add their own worklog event containing attributes but for now it looks not possible.

Hi @Patrick van der Rijst, I was able to make this work with a slight hack:

// Accessing the event is not thread-safe, so cache any
// important info locally before starting the thread.
def deleted = event instanceof WorklogDeletedEvent
def worklogId = as long
// ...

// HACK Call the API asynchronously after a delay.
// This is to allow the main thread to continue and hopefully ensure that the Tempo work attributes
// are saved. There is a miniscule chance the event will be fired before the main thread completes.
Thread.start {
def worklog = ComponentAccessor.worklogManager.getById(id)
// do somethind

This spins off a new thread and has it sleep before executing code that needs to know the values of work attributes. The gamble is that it needs the work attributes to be saved before the timer expires, so there is a slight race condition. Also, it’s important to grab the worklog id into a local variable, and then instantiate a new WorkLog object to grab any work attributes you need. Accessing the worklog event which is tossed into the script listener is inherently not thread-safe, so your event might be pointing at something else by the code inside your new thread executes.

Yeah it's tricky, I've also tried threadings and sometimes it worked, sometimes it didn't. Tempo has mentioned they're thinking of implementing their own work log event that does include worklog attributes..

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

239 views 7 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you