Conversion to Jira Standard Single Select Field

[Rajendra Kusumba]

Hi Support,

• As part of our cloud migration, we have converted a Project Specific Select Field (simple) to Jira Standard Single Select Field
• Below is the SQL update ran.

UPDATE customfield     SET CUSTOMFIELDTYPEKEY = 'com.atlassian.jira.plugin.system.customfieldtypes:select',         CUSTOMFIELDSEARCHERKEY = 'com.atlassian.jira.plugin.system.customfieldtypes:multiselectsearcher'   WHERE CFNAME = 'XXX' and         ID = 'XXX' and          CUSTOMFIELDTYPEKEY = 'jira.plugin.projectspecificselectfield.jpssf:cftype';

• After running the above query we got attached error message in field configuration scheme.
• Let us know how to handle this error.

‌

[Holger Schimanski]

Have you done a re-index?

[Holger Schimanski]

Please also comment which custom field types you want to convert. Single and Multi are described in the wiki https://bitbucket.org/hski/projectspecificselectfield-public/wiki/Home. But Simple is not described there. That would be a text field.

[Rajendra Kusumba]

We have Project Specific Select Field (simple) with values defined. We want to convert this into single select field.

[Rajendra Kusumba]

• Project Specific Select Field (simple) is a single select field type with values defined.
• Can Project Specific Select Field (simple) be converted to a Jira Standard Single Select Field ?
• Please confirm.

‌

[Holger Schimanski]

The easy conversion via SQL as described in the wiki is only possible for Project Specific Select Field and Project Specific Multi Select Field.

Converting a Project Specific Select Field (simple) to Jira Standard Single Select Field is not an easy one-step process as is technically based on a text field.

Maybe together we can create a process. I would recommend to use the Jira REST API, because this is official API for bulk changes like this. Hope you are familiar to create scripts to call the Jira REST API?

[Holger Schimanski]

As a draft proposal please see here the process via REST API

1. Retrieve the list of custom fields of type Project Specific Select Field (simple) using
   SELECT * from CUSTOMFIELD WHERE CUSTOMFIELDTYPEKEY LIKE 'jira.plugin.projectspecificselectfield.jpssf.cftype'
2. Retieve a list of the projects and their option values using
   SELECT * from AO_9661E7_SELECT_OPTION
3. Rename all custom fields and add a prefix “(legacy)” via the Jira Admin interface

4. With the list from 1. via Jira REST API

   1. Create new custom fields of type Single Select for each of the fields

5. With the list from 2. via Jira REST API

   1. Create contexts for each project of each of the fields
   2. Add option values for the context of the project of the custom field

6. Go through a bulk change process of all issues, which are using the option values and assign the respective values to the newly created Jira standard Single Select fields. (This is actually a heavy part)

‌

[Rajendra Kusumba]

• As existing Project Specific Select Field (simple) custom fields are being widely used in Jira filters and Dashboards, can we retain the same custom field and change to Jira Standard Single Select Field ?
• If we take back up of field configurations (project and option values) and issues data, after converting to Jira Standard Single Select Field and follow steps 5 and 6 as mentioned above.
• We would like to minimize the user effort on any changes to filters/dashboards by not creating a new custom field.

‌

[Holger Schimanski]

Maybe modifying the XML backup before import to Jira Cloud is an interesting option rather than using the REST API even though it is not supported by Atlassian if you have questions or issues with a hand-modified backup XML afaik.

[Holger Schimanski]

Closing this issue after no further communication for a longer time. Conversion to standard Jira custom field is possible. Best regards

Holger