Handling dependencies in JSM projects

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.

Supported dependencies for Custom Fields used on JSM projects

Dependency Type	Variables	Create issue (agent)	Edit issue (agent)	Create request (portal)
Between Connected Fields 👉 Please note that both parent and child custom fields must be displayed on screen for dependency to be effective.	`$issue.customfield_XXXX`	Supported	Supported	Supported
Current User	`$currentUser.displayName`, `$currentUser.emailAddress`, `$currentUser.accountId`	Supported	Supported	Supported
Reporter	`$issue.reporter.emailAddress` `$issue.reporter.accountId`	Unsupported (UI modification)	Supported	Unsupported (UI modification)
User Input	`$userInput`	Supported	Supported	Supported
Issue Context	`$issueType`, `$issue.key`, `$project.key`, `$issue.summary`, `$issue.priority`…	Unsupported (UI modification) Those 2 dependencies work on agent create view: `$issueType`, `$project.key`	Supported	Unsupported (UI modification) `$project.key` only
Request Context	`$project.id`, `$project.name`, `$project.key`, `$requestType.name`, `$requestType.id`…	Unsupported (UI modification) Those 3 dependencies work on agent create view: `$project.id`, `$project.name`, `$project.key`	Supported	`$project.id`, `$project.name`, `$project.key`

To go further using Custom Fields on JSM

Don’t hesitate to vote on those 2 topics to make things move forward as soon as possible!

https://ecosystem.atlassian.net/browse/FRGE-774

https://ecosystem.atlassian.net/browse/FRGE-778