-
Suggestion
-
Resolution: Fixed
-
None
-
39
-
Issue Summary
Currently, JCMA creates new filter id on cloud while migrating the JQL filters from server to cloud.
Steps to Reproduce
- Create a filter on Jira server with a simple JQL.
- Example:
project = SOFTPROJECT1
- save it as filter1.
- 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
- Create a new or sub filter with refer to the previously created one.
- Example:
filter = 123456 AND status = Resolved ORDER BY due ASC
- save it as filter2.
- Migrate all filters and Dashboard to cloud
- 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
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%=%';
- relates to
-
CONFCLOUD-78131 Entity IDs in Jira Macros should be updated after migration
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...