Handling dependencies in JSM projects | Elements Connect

Jira Service Management (JSM) projects handle custom fields differently than Jira Software projects.

This documentation provides a detailed view of which field dependencies are supported in JSM projects, based on the current technical limitations and product behavior.

JSM has three views where connected fields can be used:

View	Who uses it
Create request (portal)	Customers
Create work item (agent)	Agents
Edit work item (agent)	Agents

Before you start

Synchronize your JSM projects

A manual action is required for the initial setup and whenever you need to configure Jira field dependencies for a new portal or a new request type.

In “Settings” tab, click on the Synchronize button to be up-to-date.

Display both fields

For a dependency between two fields, both the parent field and the child field must be displayed on the screen or request form.

Supported dependencies

Views

Dependency Type	Create issue (agent)	Edit issue (agent)	Create request (portal)
Connected Fields	Supported	Supported	Supported
Current User	Supported	Supported	Supported
Reporter	Currently not supported (blocked by Atlassian)	Supported	Currently not supported (blocked by Atlassian)
User Input	Supported	Supported	Supported
Issue Context inc. Jira native fields	Supported (in 8.7.0)	Supported	Supported
Request Context	Supported	Supported	Supported

Variables reference

Dependency Type	Variables with Freemarker (preferred)	Variables without Freemarker
Connected Fields	`${issue.customfield_XXXX}`	`$issue.customfield_XXXX`
Current User	`${currentUser.displayName}`, `${currentUser.emailAddress}`, `${currentUser.accountId`}	`$currentUser.displayName`, `$currentUser.emailAddress`, `$currentUser.accountId`
Reporter	`${issue.reporter.emailAddress`} `${issue.reporter.accountId`}	`$issue.reporter.emailAddress` `$issue.reporter.accountId`
User Input	`${userInput`}	`$userInput`
Issue Context inc. Jira Native fields	`${issueType}`, `${issue.key}`, `${project.key}`, `${issue.summary}`, `${issue.priority}`… `${issue.customfield_XXXX}`	`$issueType`, `$issue.key`, `$project.key`, `$issue.summary`, `$issue.priority`… `$issue.customfield_XXXX`
Request Context	`${project.id}`, `${project.name}`, `${project.key}`, `${requestType.name}`, `${requestType.id}`…	`$project.id`, `$project.name`, `$project.key`, `$requestType.name`, `$requestType.id`…

At the moment the only Jira fields supported for dependencies are:

Select list (single choice)
Select List (cascading)
Text Field (single line)

Check documentation here for detailed referencehttps://doc.elements-apps.com/elements-connect-cloud/dependencies-on-the-issue-context

Current limitations

With 8.7.0 (October 2026)

Company-managed projects only. In team-managed service projects, the dependency does not work in the agent Create dialog because of an Atlassian bug (FRGE-2293).
Atlassian Preview feature. This relies on a Jira feature that Atlassian still labels as Preview for the JSM agent view. Its behavior may change on Atlassian's side.