-
Suggestion
-
Resolution: Fixed
-
19
-
Problem Definition
As per mentioned here, JCMA only migrate filters related to the boards from the projects you're migrating.
This means that right now, the global filters used by other entities like gadgets won't be migrated at all.
Suggested Solution
Enhance JCMA so it can migrate all instance filters and not just the filters related to the project boards.
Why this is important
When performing the entire migration via JCMA having to re-create all the global filters in Cloud can be quite toilsome depending on the number of filters you had in server.
Workaround
Please see How to migrate all boards and filters with the Jira Cloud Migration Assistant (JCMA)
- is related to
-
- Closed
-
- Closed
-
MOVE-94145 You do not have permission to view this issue
-
MOVE-94496 You do not have permission to view this issue
-
JSWM-240 Failed to load
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- relates to
-
-
-
[MIG-269] Add support to migrate global filters
Hello everyone!
It gives me great pleasure to inform you that global filters can now be migrated with JCMA as a GA feature. This feature was released with JCMA 1.10.0 and all the versions beyond it.
Here's a link to the SAC document with more information - https://support.atlassian.com/migration/docs/how-cross-project-boards-and-filters-are-migrated/
Please feel free to respond on the ticket for any follow-up questions.
Cheers
Radhika Patodiya
Product Manager, Cloud Migrations.
Hi All,
We have road mapped this feature for FY24, which is a high priority for us. We have started an investigation into providing support to migrate Global Filters through JCMA (Jira Cloud Migration Assistant). We will keep you updated on further progress.
Thanks for your patience!
Regards,
Shraddha Garg
Product Manager, Cloud Migrations
Any update / roadmap here ? Thanks to Christian for the Dark features 
This article explains how to use darkfeatures in JCMA for filters and dashboards https://confluence.atlassian.com/pages/viewpage.action?pageId=1095774091&src=jira.
Wiki page is also linked in this ticket but sometimes not shown as accessible, so maybe this link here helps some frustrated migrators until the feature is standard in JCMA.
cheers
Christian
thousands of filters that support other reporting activity outside of boards, to think that each of these would need to be re-created manually, would be a significant undertaking. I am all for clean-up, I have been doing clean-up now for a year, trying to weed out items which should not be part of the move, but if would need this issue resolved, before we could migrate.
BTW we have filters that are not only supporting Dashboards and Advanced Roadmaps, we also have filters in our confluence spaces as well as just Jira Hygiene filters that are not tied to any specific product entity.
It would be super helpful in the clean-up process if there was a way to identify filters that have not been executed in xx number of days
I think if you need to ask your users to migrate hundreds of filter, it is more frustrating than a chance.
Users will hate to use the cloud right away...
(like for Dashboards)
While I can understand the frustration in that some audiences want their new Jira Cloud environment to be exactly the same as their legacy Jira Server, we have found this is sometimes a net positive.
- It forces users to question specific filters and think about re-architecting and improving them
- It re-engages users with Jira's capabilities and gets users re-involved with things that were done a long time ago
- For us it has opened up a number of conversations around Roadmaps and Plans that is helping users see the opportunity and value of new Jira Cloud capabilities at the Enterprise level.
It is very frustrating, as show in https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/,
The "issue search filter" must be migrated, but we are missing them.
https://getsupport.atlassian.com/browse/MOVE-147256