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 you don’t have any identifier for your values available. In case you have an identifier available you should consider using the dictionary type instead.

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

{
  "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.

In the example above 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

Activate this checkbox to force deletion instead of disabling options that are no longer present in the data source.

This will also delete old references to issues. Thus, a loss of historical data is possible. Only use this option I you are aware of the consequences. Normally it is sufficient to disable an option.

Limitations

The List Type has currently a limit of 7.000 values, but keep in mind, that 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.