Users need to change their content or access to use a different email address

Jira

Confluence

• This can be resolved before the migration

Post migration:

• Please open the Problem Report ticket and share the destination cloud URL

• Please keep an eye on the Problem Report ticket as the data access might be requested

Sometimes user emails are updated but their data is still tied to the old email. When this happens, the product data has to be mapped from the old user to the new user. Then the user can use the new email to log in and will see their data. 

Pre-migration instructions:

• Jira: How to merge two users' content ownership and permissions in Jira

• Confluence: How To - Transfer Content Ownership in between Users

Jira

Option 1: REST API(only works for managed
accounts)

• Stop users from syncing through Identity
  Provider

• Get a list of managed accounts

  • Get API key and Organization ID

    • Go to Atlassian Administration and
      select your organization

    • Select Settings > API keys.

    • Select Create API key in the top right.

    • Select Create to save the API key.

    • Copy the values for your Organization ID
      and API key. Make sure you store these
      values in a safe place, as we won't show
      them to you again.

    • Select Done. The key will appear in your
      list of API keys.

  • Get managed accounts list

    • Use the GET /admin/v1/orgs/{orgId}/users request.

    • Use the API key and orgId from the previous step.

    • Use the API key with Bearer Authentication.

• アカウントの削除

  • Use the accountId, API key and Organization ID from the previous steps to delete the user account: POST /users/{account_id}/manage/lifecycle/delete.

Option 2: BulkOps App

• BulkOps App enables you to bulk delete users. Please note that BulkOps App is a third-party app that is neither built nor maintained by Atlassian.

• アカウントの削除は永続的な操作です。アカウントを再び利用する可能性がある場合、削除ではなく無効化を行うことをおすすめします。

管理対象アカウントの削除

Jira

• Use a non-production test Cloud environment. This will allow you to test from as many servers as you'd like without polluting the content in your Cloud production instance and ending up with multiple duplicates caused by testing. This is especially critical if you have existing data in your Cloud instance since there's no way of cleaning up duplicate entries(in order to wipe the duplicates for a new test run, completely reset the site and restart migration from a new server)

• If you need to perform a merge from multiple server instances, then one way to prevent duplicates is by merging the server instances first before migrating with JCMA.

Duplicates reasons:

• 複数のサーバーまたは Data Center インスタンスから 1 つのクラウド サイトに同じ名前のエンティティが移行されている

• クラウドにデフォルトで存在するエンティティで、サーバーの移行プランにも含まれるもの

• Migrating data in stages, first with Jira Site Import then followed by the Jira Cloud Migration Assistant from the same server or Data Center instance

• Custom fields could be duplicated if one of these are true:

  • different data types

  • different descriptions - even minor changes in the text will mean that fields will not match

  • different field contexts

Jira Cloud Migration Assistant での重複とエンティティの追跡

Jira

Option 1: Migrate in two steps

• First migrate all the projects of type Business (Attachment Test, Business, Migration, Test Issue Linking) followed by migration of Software project (TEST). 

• This will create only two new permission schemes for the customer

Option 2: Modify the permission grant 

• Update the permission grant for Manage Sprint permission in the Permission scheme to remove all the values from the Granted to section

• Migrating all the projects in a single plan. In this case all the projects will be mapped to single permission scheme

• Update the Manage Sprint role in the permission scheme migrated on cloud.

Permission schemes are created, for each set of "Users and roles".

Macros are not rendering correctly on Confluence pages

Confluence

All macros being used (both native and third-party) need to be tested to understand their compatibility in the cloud. 

• Macros work differently on cloud
• Learn which macros are being removed on cloud
• Assess your instance using CCMA to identify incompatible macro on cloud

Broken link fixing: links in the cloud UI pointing to the previous server or cloud URL

Jira

Confluence

• Confirm your production migration is complete

Use Product Links view

• admin.atlassian.com に移動して、組織を選択します。

• Go to Settings > Product links.

• For each product that has links you want to update, select … > Update links.

• Product links view: you need to be a site admin of the site where the product lives or an organization admin and admin of the product that has links you want to update.

• If the issue persists please open the Problem Report ticket and share the destination cloud URL

• Link fixing is done post migration and managed by the support team usually on Monday morning

• Please keep an eye on the Problem Report ticket as the data access might be requested

Links broken after Server to Cloud or Cloud to Cloud migration

Changing the indexing language after migration

Jira

Confluence

• Confirm your production migration is complete

• Open a MOVE: Problem Report ticket with the engineering team

• Include the following information:

  • the destination cloud URL that needs to be fixed

• Please keep an eye on the Problem Report ticket as the data access might be requested

Jira

• Confirm your production migration is complete

• Open a MOVE: Problem Report ticket and share:

  • the destination site

  • screenshot of the broken attachment

‼️ Workaround: refresh the page. Then the attachment preview will display as expected. 

• The fix is done post migration

• Please keep an eye on the Problem Report ticket as the data access might be requested

Projects not viewable due to permissions

Jira

• Go to  Configuration and Projects

• Identify the affected project and at the end of the project line, click on Project Settings

• On the left panel, click on Permissions.

• Choose Browse Projects permission and identify what is the Group that has this privilege.

• 管理ダッシュボードから、ユーザーをその特定のグループに割り当てます。

• If Browse Projects it’s assigned to Role only(click on the Project’s People tab and add yourself or a group to the desired Role in that project)

• If permissions are associated with Project Roles, make sure the Project Roles have groups or specific users associated with them:

  • プロジェクト ロールの管理

  • プロジェクト ロール権限を表示および編集する

移行後にプロジェクトに課題が表示されない

Boards not viewable due to the specific permissions or/and filters granted to the respective users roles, or groups

Jira

Make sure that these sanity checks are adhered while migrating boards and filters

1. ボードは有効なフィルターに関連付けられている必要があります

2. ボードの列は有効なステータスに関連付けられている必要があります

3. クイック フィルターの無効な JQL が修正されている必要があります

4. メール アドレスなどの個人データが、いずれのフィルターからも削除されている必要があります

5. 共有権限の設定が有効なグループを参照している必要があります

6. Boards/filters owned/created by inactive/deleted users must be assigned to valid owners.

• If the issue persists please open the Problem Report ticket and share the destination cloud URL

• Please keep an eye on the Problem Report ticket as the data access might be requested

Preparing boards and filters to be migrated with the Jira Cloud Migration Assistant (JCMA)

"Migrated on…" text is appearing with migrated objects such as permission scheme and custom field descriptions

Jira

• Please access the direct link for the custom fields configurations for Jira Cloud
  (https://yourcloudsite.atlassian.net/secure/admin/ViewCustomFields.jspa)

• You can check any custom fields that have the "Migrated on" note and click on the three dots > Edit details

• On the Description, you can edit as you like and click on Update.

Text updated in bulk open a MOVE: Problem Report ticket and share:

• the destination site

Give users the option to remove the migrated text from fields when using JCMA

Workflow UI status positioning is changed in the diagram view

Jira

There are no known workarounds or fixes other than to fix this manually.

Confluence

• Go to Confluence's administration and select Jira Macro Repair

• Tap the Start button

• Pop-up will be displayed, stating that "We've found some broken Jira issue macros on your instance"

• Tap the Click here to fix button.

• If you have only a single application link, tap the Finish button to perform the repair. If there are different application links connected, tap the Select an Application Link dropdown in order to confirm the correct one and tap Finish.

• If the Jira content has not been imported, the Jira issues will not be located at the target's Jira instance linked to Confluence, meaning that they can be only "repaired" if an application link is created to the source where the Confluence import came from and then, the remap would be performed.

• If the issue persists please open the Problem Report ticket and share the destination cloud URL

• Please keep an eye on the Problem Report ticket as the data access might be requested

Jira マクロの修復を利用する

Confluence

• Use the team-calendars migration script

• Please see the README for details on supported and unsupported calendar events. For instance, Jira Project Events are not migrated.

Script to migrate Confluence team calendars from server to cloud

Not all space content is viewable to users due to permissions migration

Confluence

Recover permissions to the site:

• Select the gear icon in the top nav(top right) to go to product settings.

• Select Space Permissions.

• Locate the space in the Individual Spaces list and select Recover Permissions.

• If you're an admin in the space, you'll see Manage Permissions.

• Selecting Recover Permissions will be recorded in the Confluence audit log.  

This may present as:

• スペースのドロップダウンにスペースが表示されない

• [すべてのスペースを表示] またはスペース ディレクトリでスペースが見つからない

• スペースのコンテンツを検索できないか、検索でフィルターとして利用できない

移行後にスペースのページとコンテンツが表示されない

Pages are not displaying correctly due to being migrated with the old editor

Confluence

When page conversion is turned, you'll get a banner notification at the top of the first page and you’ll see a notification at the lower left of the page. Before clicking convert, you have a chance to see how the page will look in the new editing experience.

• Click Preview page.  More detailed information is presented about the process.

• Click Convert page.  Page refreshes, and the content appears in the new editor.

• Click Publish… to save the new editor version of the page.

• The New editor: Includes Publish… or Update and Close buttons in the top menu and the emoji icon

• The Legacy editor: Has earlier versions of text-color picker and page formatting

ページを新しいエディタに変換する