JIRA Cloud Migration workaround

[Baybars Kumbasar]

Fields created by Project Specific Select Fields do not migrate to Jira Cloud. I know that you do not plan to support Jira Cloud for the foreseeable future, so do you suggest a workaround for the users?

[Holger Schimanski]

This depends a little on the custom field type you have used.

Which of the custom field types are you using?

• Project Specific Select Field

  • Is under the hood based on a standard single select field

• Project Specific Multi Select Field

  • Is under the hood based on a standard multi select field

• Project Specific Select Field (simple)

  • Is actually a standard text field under the hood.

You can change these custom field types via some SQL scripts from Project Specific to standard Jira fields. In the wiki https://bitbucket.org/hski/projectspecificselectfield-public/wiki/Home you find SQL scripts to “Convert Standard Single and Multi Select Field to Project Specific Select Field”.

In your case now you want to convert the Project Specific Select Field in the other direction back to Standard Single and Multi Select Fields, so you have to translate the actual SQL queries.

Do you have the required skills for such activity? Do you have a test environment, where you can test this conversion?

After the conversion to standard fields you can configure the fields still in the same way via https://support.atlassian.com/jira-cloud-administration/docs/configure-custom-field-context/. But now the Jira admin has to do the task. The Project admin is not able to modify the option values anymore.