Use List if you want a synchronise a simple list of string values with your Jira custom field. You should use this type only if your values don’t have an identifier. In case you have an identifier available we recommend using the dictionary type instead.

In the following, we will use a data source with this JSON result as example:

{
  "userlist": [
    {
      "id": 1,
      "name": "Mario Speedwagon"      
    },
    {
      "id": 2,
      "name": "Anna Sthesia"      
    }
  ]
}
JSON

Select Result

Transform the raw result of the data source into a list of values. You can use filter and selection mechanics of Xpath or JsonPath. JsonPath.com is a great helper tool to get more complicated transformations done.

Given the above example, the jsonPath would look like this:

$.userlist[*].name
CODE

This expression selects all items from the userlist by using the [*] and extracts only the name field. The result of this expression is:

[
    "Mario Speedwagon",
    "Anna Sthesia"
]
CODE

This means that those two values will be synchronized into the target custom field selected later.

Keep in mind that the values must be unique. An custom field of type select doesn't allow duplicate values

Force Delete

By activating this checkbox, the app will force delete missing values instead of disabling values which are no longer present in the data source.

This will also delete former references to issues. Thus, a loss of historical data is possible. Only use this option if you are aware of the consequences. Usually it is sufficient to just disable a value.

Limitations

List Type currently has a limit of 7.000 values. But keep in mind: At around 2.000 entries, the dropdown performance in the issue view starts to decrease drastically. It also depends on the machine you are testing it on, so make sure your userbase can use it properly.