Wasn't able to access hello.atlassian.net - but the release notes for 1.7.8 are also here:
https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant/version-history

Update: 23rd Feb, 2023

The feature to migrate share permissions along with its rights is now available to all the customers using JCMA 1.7.8 and above versions.

Regards,
Mandeep Kaur

@Mandeep,

hello.atlassian.net is not accessible for non-Atlassians. Where can we find more info on publicly available pages?

Hi All,
We have released this fix behind the FF in JCMA 1.7.7 release.
You can use this by enabling the following feature flag `com.atlassian.jira.migration.pass.share.permission.with.rights`

You can find more info here
https://hello.atlassian.net/wiki/spaces/CR/pages/2228533275/Migrations+Release+Readiness+Migrating+Share+Permissions+Filters+Dashboards+SWAT+ONLY

Still no fix for this very important feature ?? it will be impossible to do this manually for over a 10 000 filters for different users and groups... Please fix this ASAP.

Appears to also affect JCMA 1.7.7

Any progress here ??

This is annoying why JCMA doesn't support this feature. If such basic support is missing why Atlassian took a decision to stop Jira Server support. Imagine fixing this for more than 3000 filters manually, it's completely unacceptable

We have more than 1500 filters with multiple editors. Imagine how much time it's going to take to fix those manually...

It's incredible how many essential features are missing from the Cloud Migration tool. Atlassian has been pushing for this migration for years, and everything utterly sucks.

At this point, it would be easier to Atlassian to go back to supporting Jira Server.

Andy - what happened?
New JCMA version has released and this does not appear to have been included...

My migration support team hasn't been able to offer any other solutions, so we're still stuck unable to migrate.

See MIG-1043.

Hi Mark, 

My name's Andy and I'm one of the escalation managers here at Atlassian. We want to assure you that this bug/missing feature is definitely in our radar due to the impact and lack of official workaround. We're working with Product Management to get an official fix out tentatively for the next JCMA release. I see that you have an active ongoing migration, so I will work with your Cloud Migration Manager to provide you with any options we have available until the next release.

Thanks!

Andy Jean

Hi Mandeep, 

It seems like you've completely edited out the line about a workaround existing.
Is there something available to fix my problem, or is there nothing currently?

Cheers,
Mark.

Hey Mark,
Apologies for the delay, as I have been waiting for Saif to reply to this comment but given it was long weekend in India, he was not available.
To summarise the progress,
SWAT is still working on the permanent fix and its in development phase.

Thanks.

Hi Mandeep,

I believe that I'm potentially being blocked by the issue in our migration testing see - MOVE-81652 and was linked here.
In my case it is not a group, but an individual user listed in the filter share (my user account),

Based on your workaround: "Currently, there is no known workaround for this behavior at scale. You will have to manually update the permissions post-migration."

Can you clarify on how one would do this as a Site/Global admin in Jira Cloud?
I cannot actually see the filter on the Cloud side to fix any permissions (which I assume explains why the corresponding board shows as "private" to my user login). 

As we no longer have direct access to the database do you mean that ATL Support would need to manually fix this on my behalf?

Cheers,
Mark.

SWAT will start working on providing a fix for this. Will provide a ticket detail here once we kick off the work.

This particular issue is not a bug but a missing feature in JCMA since quite some time now.
JCMA doesn't have the capability of migrating share permissions yet.

If/when we need to resolve this, it will be taken as a feature and will require time to develop and make it available to GA.

But for now, we are gathering impact to provide resolution for it.

Meanwhile, the workaround for this problem will be to edit/add the share permissions on cloud manually.