/
Use Case Scenarios

Use Case Scenarios

Owned by Werare Support User
Last updated: May 25, 2023
4 min read

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.

While defining your data source, you need to provide an endpoint that allows you to test the connection.
Configure the projects and issue types
Set Affected Field. To trigger the behavior when “Assignee” field changes, select “On Change”.
As the behaviour will run whenever Assignee field changes, None is chosen as Condition.
To fetch assignee ssn from your external data source, add an external parameter after choosing “Set Value” operation type and “Advanced Configuration”.
The demo endpoint used for this example takes the account id of the user as url parameter (https://xxx/ssn?accountId=xxx). Therefore the key was set as accountId. Also, to get the value of the Assignee field double curly bracket notation needs to be used. The endpoint returns a JSON response with “ssn” field in it. JSON path to the actual value in the response should be specified.
The value of the field will be equal to the value of the assigneeSsn external parameter. While using external parameters inside Jira Expressions again double curly bracket notation needs to be used.
The field is also made read only to prevent any other users to change it.
This is how Assignee SSN looks like after setting Assignee on the issue create view.

The app sends request to your external APIs over Atlassian servers. If your external APIs are protected, you need to follow the instructions in IP addresses and domains for Atlassian Cloud products | Atlassian Support 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.

To get the value of Priority field, double curly brackets are used. Then, name field of the value is compared to “High”.

To learn about field shapes of the system and custom fields, you can refer to the UI modifications.

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 the value of the field to project lead, the Jira expression should return the accountId of the project lead for the current project.

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.

Related content