Certain Issue filter no longer function as expected after migrating from Jira Cloud to Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After migrating from Jira Cloud to Jira Data Center (DC), users may encounter an issue where certain issue filters no longer function as expected. Specifically, filters that include customfields in formats like '<customfield-name>[Radio Buttons] or <customfield-name>[Dropdown]' will not work in Jira DC. This is due to differences in how Jira Cloud and Jira DC handle custom fields syntax in JQL (Jira Query Language).
Cause
In Jira Cloud, issue filters may include custom fields formatted as 'customer[Radio Buttons]' (e.g., Teams[Radio Buttons]) or 'customfield[Dropdown]' (e.g., Stakeholder[Dropdown]), or similar formats. However, this format is not compatible with Jira Data Center, and as a result, any issue filters using this syntax will fail after migration.
Solution
To resolve this issue, the JQL queries associated with the problematic issue filters need to be updated in the Jira DC database. Here are the steps to Apply the Solution:
Stop Jira service
Take a backup of Jira database
Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.
Run the SQL Query
DB Query
1UPDATE searchrequest SET reqcontent = REGEXP_REPLACE(reqcontent, '(?<!cf)\[([^]]+)\]', '', 'g');Example
A sample JQL Query from Jira Cloud not compatible with Jira DC:
project = TEST AND "Stakeholder[Dropdown]" != Test01 AND "TEAM[Radio Buttons]" != Test02 ORDER BY cf[12000] ASC
JQL Query after running the above mentioned UPDATE SQL command which makes the same JQL compatible with Jira DC
project = TEST AND "Stakeholder" != Test01 AND "TEAM" != Test02 ORDER BY cf[12000] ASC
Start Jira service
Was this helpful?