ScriptRunner Database Picker field fails during CSV import

[AishwaryaJ]

Hi Community, We are migrating issues from one Jira instance to another using native CSV import. We have a custom field of type Single Database Values Picker field.

During the CSV import:

When we provide the display name (text value) in the CSV, the import fails with an SQL-related error.

When we provide the option ID the issue gets created successfully, but the custom field and value does not populate in the Jira UI.

We would like to know:

1. Is it possible to populate a ScriptRunner Database Picker field using Jira native CSV import?

2. If yes, what is the correct value format that should be provided in the CSV file?

Any guidance or suggestions would be appreciated.

Thank you.

[Arkadiusz Wroblewski]

Hello and welcome to the Community @AishwaryaJ 

A ScriptRunner Database Picker stores the underlying row ID rather than the display text. If your CSV contains the display name, the validation SQL fails; if the imported ID stays blank, that ID either does not exist in the target database or the target SQL is failing to resolve it.

You need to update your CSV to use valid target-side database IDs, ensuring those rows exist and the target SQL query successfully returns them. Since this is a specialized app field, reach out to Adaptavist Support if you still hit native Jira CSV import problems. They should be able to help you with Troubleshooting.