Issue Summary

When Kanban board sub-filter is using custom JQL and migrated using JCMA, it gets replaced with the default JQL. The sub-filter JQL is not getting included in the export hence it is set to default. Example: One of the Kanban board sub-filter is configured with the below JQL

type = "Test Execution" AND "Test Campaign" in unreleasedVersions()

After migration, they all replaced with the following query :

fixVersion in unreleasedVersions() OR fixVersion is EMPTY

It breaks all kanban boards after migration.

This is reproducible on Data Center:

Steps to Reproduce

1. Create a Kanban project or board
2. Navigate to Configure -> General
3. Configure a custom JQL in Kanban board sub-filter
4. Migrate this project using JCMA
5. After migration JQL is replace with default JQL(fixVersion in unreleasedVersions() OR fixVersion is EMPTY)

Expected Results

JCMA should retain the filter configured in the kanban sub-filter

Actual Results

The sub-filter JQL is replaced with the default JQL.

Workaround

Manually update all the Kanban board sub-filter JQL after migration. SQL query to identify all the boards using the subfilter.

Select RA."NAME", SU."LONG_QUERY" 
from "AO_60DB71_RAPIDVIEW" RA 
JOIN "AO_60DB71_SUBQUERY" SU ON SU."RAPID_VIEW_ID"=RA."ID"