/
Jira Agile and Jira Tempo replacement variables

Jira Agile and Jira Tempo replacement variables

Jira Agile replacement variables

The following replacement variables are available when working with Jira Agile actions. These variables store references to the last created, found, or explicitly referenced objects during CLI execution.

Variable

Description

Since

Variable

Description

Since

board

Last created, found, or referenced board name

7.8

boardId

Last created, found, or referenced board ID (numeric)

7.8

Jira Tempo replacement variables

Use these replacement variables with Jira Tempo to refer to the most recently used or created entities during CLI execution. These variables are helpful when chaining actions or processing lists of Tempo-related data.

Variable

Description

Since

Variable

Description

Since

account

Last referenced account key

7.3

accountId

Last referenced account ID (numeric)

7.3

accountName

Last referenced account name

7.3

accountLinkId

Last referenced account link ID

7.3

category

Last referenced category key

7.2

categoryId

Last referenced category ID (numeric)

7.3

categoryName

Last referenced category name

7.2

customer

Last referenced customer key

7.2

customerId

Last referenced customer ID (numeric)

7.2

customerName

Last referenced customer name

7.2

member

Last referenced member name

7.2

team

Last referenced team name

7.2

teamId

Last referenced team ID (numeric)

7.2

worklogId

Last referenced worklog ID

7.3

Common client variables

These variables are available across multiple clients and use cases. They provide context and metadata for actions executed in a script or command series.

Variable

Description

Since

Variable

Description

Since

entry

Current entry from the list parameter in runFromList

—

entry2

Current entry from the list2 parameter in runFromList

—

renderRequest

Last result from the renderRequest action, modified by findReplace

—

server

Server URL for clients accessing a remote server

9.0

hosting

Hosting type returned by getServerInfo (server, cloud, or datacenter)

9.3

version

Version value returned by getServerInfo

9.3

runDate

Timestamp of the first action that references this variable in a run script

9.0

 

  • Same value used across subsequent actions in the script for consistency

 

 

  • Follows format defined by dateFormat, or the default format

 

file

Path to file used by the last get or getList action with the file parameter

9.3

fileSize

Size of the file retrieved using the file parameter

9.3

fileContent

Content of the file (text only, limited to files under 10 MB)

9.3

Usage tips and additional notes

  • Use variable syntax as @<variable>@ in your commands. For example: @entry@, @issueId@, or @runDate@.

  • Variable names are case-sensitive.

  • Variables are available only within the current run scope or a parent run action. Sibling runFromList executions do not share variables.

  • Variables are set based on the last created (for create, add, etc.) or last referenced (from get, runFromList, etc.) item.

  • Use the getReplacementVariableList action to list currently defined variables, excluding built-in variables like server or runDate.

  • Use the setReplacementVariableList action to define your own custom replacement variables.

  • The reference parameter allows setting custom variable names based on the result of an action. These are useful when you want to retain a specific value throughout a longer script.