[MIG-1088] Boards/Filters/Dashboards edit permissions are not migrated via JCMA

Andrew T made changes - 09/Feb/2024 6:10 AM

Status

Original: Closed [ 6 ]

New: Closed [ 6 ]

Andrew T made changes - 09/Feb/2024 6:08 AM

Resolution	Original: Fixed [ 1 ]	New: Obsolete [ 11 ]
Status	Original: Closed [ 6 ]	New: Closed [ 6 ]

Shraddha Garg (Inactive) made changes - 30/Oct/2023 10:06 AM

Remote Link

New: This issue links to "Page (Confluence)" [ 831522 ]

Lucas Tambosi made changes - 09/Mar/2023 7:03 PM

Remote Link

New: This issue links to "MOVE-120375 (Atlassian Support System)" [ 739167 ]

Mandeep Kaur (Inactive) made changes - 23/Feb/2023 12:54 AM

Description

Original: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

*Workaround:*

Download the latest version (1.7.8) of Jira Cloud Migration Assistant from [#[https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant/version-history]]
* Start your migration as usual.
* This feature will now migrate the share permissions for the filters and dashboard along with its rights i.e. edit and view

New: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

*Workaround:*

Download the latest version (1.7.8) of Jira Cloud Migration Assistant [[https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant/version-history]]
* Start your migration as usual.
* This feature will now migrate the share permissions for the filters and dashboard along with its rights i.e. edit and view

Mandeep Kaur (Inactive) made changes - 23/Feb/2023 12:53 AM

Description

Original: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

*Solution:*

The fix for this issue has been released in [JCMA 1.7.8|[https://marketplace.atlassian.com/download/apps/1222010/version/100700722]].
This feature will now migrate the share permissions for the filters and dashboard along with its rights i.e. edit and view

New: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

*Workaround:*

Download the latest version (1.7.8) of Jira Cloud Migration Assistant from [#[https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant/version-history]]
* Start your migration as usual.
* This feature will now migrate the share permissions for the filters and dashboard along with its rights i.e. edit and view

Mandeep Kaur (Inactive) made changes - 23/Feb/2023 12:47 AM

Description

Original: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

New: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

*Solution:*

The fix for this issue has been released in [JCMA 1.7.8|[https://marketplace.atlassian.com/download/apps/1222010/version/100700722]].
This feature will now migrate the share permissions for the filters and dashboard along with its rights i.e. edit and view

Osimar Medeiros made changes - 23/Feb/2023 12:42 AM

Remote Link

Original: This issue links to "Page (Atlassian Documentation)" [ 662445 ]

Mandeep Kaur (Inactive) made changes - 23/Feb/2023 12:36 AM

Description

Original: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.

h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.
h3. Workaround

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

New: h3. Issue Summary

When customer migrates Jira from Server/DC to cloud using 1.6.5 or 1.7.1, the edit permissions on the filters, boards is not migrated.
Same is the case with dashboards as well.
h3. Steps to Reproduce
* Install JCMA 1.6.5 or 1.7.1
* Enable below dark features:
{color:#ff0000}com.atlassian.jira.migration.export.all.filters
com.atlassian.jira.migration.export.multiprojects.boards{color}
* Create a project and then create a board in this project.
* Go to board settings and edit filter associated with it.
* Add any group/user to view permissions on the filter.
* Add any group/user to edit permissions on the filter.

h3. Expected Results

Both view and edit permissions should get migrated to Cloud for the filters and board.
h3. Actual Results

Only view permission is migrated to the cloud, and the group that was added in edit permissions will be visible under view permissions. The edit permissions will become private.
On Server, before migration:
!image-2022-07-07-15-20-50-845.png|thumbnail!
On Cloud, after migration:
!image-2022-07-07-15-21-21-466.png|thumbnail!

!image-2022-07-07-15-24-33-254.png!
It can be seen clearly, that jira-users group was part of edit permissions for the filter on Server, but after migration, on cloud, it is added to view permissions.

Mandeep Kaur (Inactive) made changes - 23/Feb/2023 12:25 AM

Link

New: This issue resolves ~~MIG-1043~~ [ ~~MIG-1043~~ ]

Details

Description

Issue Summary

Steps to Reproduce

Expected Results

Actual Results

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates