To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »


For the above versions of the Tempo add-ons we implemented a change on how the Tempo Team custom field is returned from the Jira SPI. This change affects possible integrations and apps that work with Tempo. 

We are now returning a Team object instead of the Team ID only. The class we changed is named TeamCustomField and it is implementing the CustomField Jira SPI.

The Custom Field SPI is documented here:
https://docs.atlassian.com/software/jira/docs/api/8.0.0/com/atlassian/jira/issue/fields/CustomField.html
And the method in question is getValue.

That means that if you have implemented a solution like this:

var teamCustomField = customFieldManager.getCustomFieldObjectByName('Team')

var teamId = teamCustomField.getValue(issue)

It will fail and it needs to be changed to:

var teamCustomField = customFieldManager.getCustomFieldObjectByName('Team')

var teamId = teamCustomField.getValue(issue).getId()


If you encounter issues and require more information, please contact our Support team


  • No labels