Use Case Scenarios
Using Field Behaviours for Jira Cloud, you can establish a relationship between fields on the issue create screen, enabling dynamic updates based on changes in specific field values. With this functionality, you can define dependencies between fields, ensuring that when one field is modified, the value of another field automatically adjusts to reflect the updated information. This feature streamlines the issue creation process, improves data accuracy, and enhances overall efficiency by automating the synchronization of related field values within Jira.
In the example below, Assignee SSN field is automatically set when Assignee field is modified. This example uses “Advanced Configuration“ feature with external parameters.
1- Configure your external data source to retrieve assignee ssn info.
The app sends request to your external APIs over Atlassian servers. If your external APIs are protected, you need to follow the instructions in https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/ to provide access to the requests coming from the IP ranges of Atlassian servers.
A field can be made required according to the value of another field. In the example below, when the priority is High, Assignee field will be required to create the issue.
Field Behaviors for Jira Cloud enables you to assign different names/descriptions to Jira fields to customize your issue create view.
In the example below, first the description for “Contact person” field is changed. Then, its value is set to the project lead.
To set value for a user single select field (or assignee, reporter and people fields) with Advanced Configuration, the result of the Jira Expression should be an accountId. Similarly, to set value for a user multi select field, the result should be a list of accountIds.