Currently, accessing and setting values for Tempo fields in Jira Automation requires Global Jira Administrator permissions. This restriction limits the ability of Project Administrators to fully manage automation rules involving Tempo fields, as they can only view global automation rules and manage project-scoped ones. The need for global permissions arises when making API calls to retrieve fields and their options, which is necessary for interacting with Tempo's custom fields created by the Forge(Connect) app.

Users, particularly those without Global Jira Administrator permissions, encounter difficulties when attempting to use the "Choose field to set" dropdown in Jira Automation, as it does not return Tempo fields. This results in an error, limiting the functionality and accessibility of automation involving Tempo fields for non-global users.

Current Workaround:

Users with knowledge of the custom field ID can set the value of a Tempo account field without Global Jira Administrator permissions. This involves using the Advanced Edit feature in the edit issue field section of automation rules, with a JSON structure like:

{
  "fields": {
    "customfield_12401": "ID number"
  }
}

In this JSON example, "customfield_12401" represents the custom field ID of the Tempo account, and "ID number" should be replaced with the actual ID of the desired value.