While configuring custom fields introduced by JQL Issue Select app, you can use various Token Strings in your settings (JQL Pattern and View Pattern settings) to get dynamic behavior.

The Token Strings are placed into text between curly braces and are calculated when the field is displayed on screen. Each text can contain more than one Token String:

For ex:

Let's consider the following Jira issue:

Issue FieldValue

My sample issue

If you setup a JQL Advanced Field to have the following configuration, the calculated values for ABC-123 will be like:

JQL Advanced Field

Config Field

ValueCalculated Value for ABC-123
JQL Patternproject = {issue.projectkey}project = ABC
View Pattern{issue.key} - {issue.summary}ABC-123 - My sample issue
Value Pattern




The Token Strings that will be processed must be placed between curly braces. Ex:

assignee = {issue.assignee}

A token string can have a chain of Tokens, connected by a period.

project = {issue.project.key}

The first token of each token string must be one of the following:

  • issue
  • project
  • parent
  • currentuser

All these tokens return Objects and may or may not be followed by other tokens.

If not followed by other tokens, these tokens return the default text values representing those objects. {issue} returns the issue's key, {project} returns the current project's key, {parent} returns the issue's parent issue's key and {currentuser} returns the logged in user's username.

If followed by other tokens, next tokens in the chain also may return Text values or Object values. For ex: {issue.summary} returns a text that contains the summary of the issue. {issue.project.key} returns a text that is the key of the project that issue belongs to. ( {issue.project} returns a Project object and the key token returns the key of that project object. )

For possible Object types and tokens that can follow each of those object types, please see JIS v2.0 - Tokens Reference

Responding to field value changes on the same screen

Currently, other field references work based on field values persisted to the data storage, so does not immediately respond to referenced field value changes on a create, edit or transition screen.

Responding to changes on the same screen is definitely in our roadmap. Please tell us about your use cases for this feature by sending us an email to .

  • No labels