Dependencies on the issue context

The dependencies detailed in this page are specific to connected custom fields.

When fetching data from an external source, it can be useful to only retrieve data that is relevant to the current issue, even if it is still being created.

To do that, Elements Connect allows you to reference specific variables and attributes when setting up your query, which can be used to create dependencies to other Jira fields in the same context. This context can be the issue view, or even the issue creation screen.

Please note, this section does not concern custom fields displayed on Jira Service Management (see below).

Configuration

Since version 2.13.0 of Elements Connect (released in August 2025), the possibility for Jira fields dependencies for create screens is automatically handled upon project and work types creation.

Connected fields can interact with Jira native fields without the need of manual configuration.

Supported fields

The table below lists all the fields that can be referenced in your queries, as well as the attributes you can use for these fields.

Field type	Available attributes	Value returned
Project key	`$project.key`	Key of the current project
Issue key	`$issue.key`	Key of the current issue
Summary	`$issue.summary`	Summary of the current issue
Issue type	`$issueType`	Name of the current issue type
Priority	`$issue.priority`	Priority of the issue
Parent	`$issue.parent`	The Parent of the work item (for example, its Epic)
Assignee	`$issue.assignee.emailAddress`	Email of the assignee on the issue
	`$issue.assignee.accountId`	Atlassian account ID of the assignee of the issue
	`$issue.assignee.displayName`	Name of the assignee on the issue
Reporter	`$issue.reporter.emailAddress`	Email of the reporter on the issue
	`$issue.reporter.accountId`	Atlassian account ID of the reporter of the issue
	`$issue.reporter.displayName`	Name of the reporter of the issue
Select List (single choice)	`$issue.customfield_xxxxx`	Displayed value of the option selected in the select list
Text Field (single line)	`$issue.customfield_xxxxx`	Raw text value
Date Picker	`$issue.customfield_xxxxx`	Date in “yyyy-mm-dd” format
User Picker (single user)	`$issue.customfield_xxxxx.accountId`	Atlassian account ID of the user selected
	`$issue.customfield_xxxxx.emailAddress`	Email of the user selected
	`$issue.customfield_xxxxx.displayName`	Name of the user selected
Number	`$issue.customfield_xxxxx`	Number value

Usage

You can use these attributes to create dependencies in your connected custom fields queries to other Jira fields.

For example, you may want to create a dynamic query in a REST endpoint that returns only the data based on the issue type of your current issue.

API request

CODE

{BaseURL}/search/jql?jql=issuetype="$issuetype"

In this request to the local Jira API, all the issues with the same issue type as the current issue are retrieved.

Known limitations

Value not selected in the connected custom field after a refresh

If you are using a connected custom field with a dependency, the option selected in the custom field will be automatically unselected if the value of the parent field changes.

For example, let’s say your connected custom field has a dependency to the summary of your issue, and that you have selected an option in your custom field.
If the value of the summary is updated, the options of your connected custom field will be automatically refreshed. Even if the value that was selected remains a valid option, it will not be selected anymore and you will have to select it once more manually.

Issue context is not available on JSM projects

If you’ve decided to displayed your connected custom field on a JSM project, then you might face errors using those dependencies. This is unfortunately due to an Atlassian limitation regarding UIM not being available on Jira Service Management.

Atlassian’s ETA for this feature is the very end of 2025. As soon as they make it possible, we will make sure that Elements Connect allows dependencies to custom fields in JSM projects.