Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why is our static list work attribute not returning correct values?

Edward
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 24, 2025

Hi,

I've created a new work attribute (see attached screenshot) as a static list following the link below.

https://help.tempo.io/timesheets/latest/creating-work-attributes-for-customized-time-loggi

screenshot.png

When we retrieve the roles from the tempo API (https://api.tempo.io/4/worklogs), we are getting values like ProjectManager, SeniorDeveloper, SolutionArchitect.

Why are the spaces being removed? For some roles we are getting guid values like ff4e0c04-1464-473a-acec-bacc1d374fff, fa0236e8-4886-4172-935b-fe38332d0197, etc. Anyone knows why this is happening and how we can retrieve the roles properly?

1 answer

0 votes
Mercy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 10, 2025

Tempo’s REST API returns static-list work attribute values in their stored key form, not their label. When you create a static list in Tempo Settings > Work Attributes, each option is saved with a key (no spaces, often camelCase) and a display name. The `/worklogs` endpoint exposes the key so it can be used consistently across systems. That’s why you see `ProjectManager` instead of “Project Manager.” If you didn’t manually define keys when creating the list, Tempo automatically generates GUIDs, which explains the long UUID-style values.
To display the readable names, you need to map those keys or GUIDs back to their display labels using the [Tempo Work Attribute API](

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events