We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-303

Add-on users are not migrated with space permissions

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When a customer preps their cloud site by installing an app they want to migrate, the add-on user is added to the cloud site. After setting up their cloud site, when they migrate space and page content via the Confluence Cloud Migrations Assistant (CCMA) or via manual import of the Space, the add-on permissions are not updated for the imported space. This means the add-on will work in new spaces but not in migrated spaces.

      As a workaround, the customer would need to re-install the app on the cloud site post migration to have the add-on user added to space permissions for all spaces. Or update the space add-on permissions.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Migration Platform'
            1. Migration Platform
            2. MIG-303

            Add-on users are not migrated with space permissions

              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                When a customer preps their cloud site by installing an app they want to migrate, the add-on user is added to the cloud site. After setting up their cloud site, when they migrate space and page content via the Confluence Cloud Migrations Assistant (CCMA) or via manual import of the Space, the add-on permissions are not updated for the imported space. This means the add-on will work in new spaces but not in migrated spaces.

                As a workaround, the customer would need to re-install the app on the cloud site post migration to have the add-on user added to space permissions for all spaces. Or update the space add-on permissions.

                        jrichards@atlassian.com James Richards
                        akassab Alex
                        Votes:
                        5 Vote for this issue
                        Watchers:
                        12 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            jrichards@atlassian.com James Richards
                            akassab Alex
                            Votes:
                            5 Vote for this issue
                            Watchers:
                            12 Start watching this issue

                              Created:
                              Updated:
                              Resolved: