Issue Summary

Currently, JCMA creates new filter id on cloud while migrating the JQL filters from server to cloud.

Steps to Reproduce

1. Create a filter on Jira server with a simple JQL.
2. Example:

   project = SOFTPROJECT1

1. save it as filter1.
2. Get the filter id on server(Jira server > Issues > Manage filters > Click filter1 > Look for id on the browser URL). In our case filter1 has id 123456
3. Create a new or sub filter with reference to the previously created one.
4. Example:

   filter = 123456 AND status = Resolved ORDER BY due ASC

1. save it as filter2.
2. Migrate all filters and Dashboard to cloud
3. Filter does not work as expected due to JQL on Cloud stores filterid instead of filtername
   Example:

   filter = 123456 AND status = Resolved ORDER BY due ASC

   Error:

   A value with ID '123456' does not exist for the field 'filter'.

Expected Results

JQL filter to work using the filtername instead of filter id or Map the Updated filter ID to the JQL query that used the "filter =", "filter !=" or "filter in ()" clause.

Actual Results

A value with ID '123456' does not exist for the field 'filter'.

Workarounds

• Replace sub filter field with the actual field on JQL.

  project = SOFTPROJECT1 AND status = Resolved ORDER BY due ASC

(OR)

• Use the filtername instead of id in the subfilter

  filter=filter1 AND status = Resolved ORDER BY due ASC

Note:
Verify there is no filter contains id on Jira server database by executing following query.

select filtername from searchrequest where reqcontent like '%filter%=%';