Migrate between team-managed and company-managed spaces
このページの内容は、次のような場合に役立ちます。
Your team currently works in a company-managed space, and you want to migrate to a team-managed space.
Your team gave team-managed spaces a try, found that it didn't suit how you work, and you want to move your work items to a company-managed space.
You must have the following to do the things described on this page.
Role: Space admin
Permission: Administer spaces, Browse spaces
Create a space to receive your existing work items
You'll need to have a new scrum or kanban space available, so the work items in your current software space have a place to go to.
Create a new team-managed space to receive work items in your existing company-managed space
To create a new team-managed space:
Next to Spaces in the sidebar, select Create space ().
Select either the Work management or Software development template type in the sidebar, or select Jira under Apps.
Select a template for your team.
View the detailed information on the template and select Use template.
Select how to manage your space: Team-managed.
Give your space a name. You can change your template by selecting Change template.
Choose who can access your space.
[作成] を選択します。
We automatically generate a space key when the space is created.
Or, create a new company-managed space to receive work items from your existing team-managed space
If you want to move from a team-managed space to a company-managed space, your Jira admin will need to create a new company-managed space for you. Reach out to them for help.
To create a new company-managed space:
Next to Spaces in the sidebar, select Create space ().
Select either the Work management or Software development template type in the sidebar, or select Jira under apps.
Select a template for your team.
テンプレートの詳細を表示して、[テンプレートを使用] を選択します。
Choose how to manage your space: Company-managed.
Give your space a name. You can change your template by selecting Change template.
Choose who can access your space.
[作成] を選択します。
Find and move existing work items to your new space
Now that you have an empty space waiting to receive your old space's work items, it’s time to move some your existing work items into the new space.
Select Search in the top navigation, then select View all work items.
Select More actions (), then select Bulk change work items.
To move multiple work items using the All work view:
Adjust the search criteria to show the appropriate list of work items.
Select More actions (), then select Bulk change work items.
Select the work items you'd like to perform the bulk operation on, and select Next.
Select Move work items and select Next.
Select a destination space and work type, and select Next.
この移動に必要なフィールドの値を選択し、可能であれば、メール通知を送信するかどうかを決定します。[次へ] を選択します。
変更を確認して [確認] > [承認] の順に選択します。
We’re merging the All work view with the List. If you can’t see All work in your space navigation, you’re already viewing the new List experience. The features described on this page are relevant for both experiences. Read more about the merge
企業管理対象からチーム管理対象プロジェクトへ移行する際の考慮事項
Team-managed spaces and company-managed spaces are technically quite different. Here's a few things to consider when you migrate from a company-managed software space to a team-managed software space:
Completed, planned or active sprints: Sprints won’t move from a company-managed space to a team-managed space. Past sprints won't be displayed on the timeline. The work items that were in your company-managed space will be added to the backlog of your team-managed space.
Components: Component fields are unique to every space in Jira. If you migrate work items with completed component field information, you will lose this data.
Components field data is not recoverable, even if you bulk move these work items back to the company-managed spaces they came from.
カスタム フィールド
These must be recreated in your new team-managed space. Team-managed space fields are independent from global custom fields. When you move work items to a team-managed space, Jira retains most of your work items' global custom field values (except component and version fields). But, we don't map them to your team-managed space's fields.
Your global custom field data is stored against your work items but the fields in your company-managed space are technically different from the fields in your team-managed destination, so they will appear blank. This data is not lost (except component and version fields). If you move your work items back to a company-managed space that supports the custom field, the original values stored against it reappear.
Story points estimation: This data will be lost, however you'll be able to start using story points estimation by enabling the Estimation feature in your team-managed space.
Reports: Data for your space's Velocity report won't be saved. The Velocity report will show that no points were completed in past sprints.
レポート履歴: この移行プロセスでは、すべてのレポート履歴が失われます。バーンアップ レポートとベロシティ レポートは移行されません。
Parallel sprints: Currently, team-managed spaces don’t support running parallel sprints.
Space and work item keys: Jira will automatically update the work item keys of migrated work items to reflect their new space. Any existing links to old work item keys will be automatically redirected.
Versions and releases: Any version information is lost in this migration process, even if you have the Releases and versions feature enabled in your new team-managed space.
Versions and releases field data is not recoverable, even if you bulk move these work items back to the company-managed spaces they came from.
チーム管理対象プロジェクトから企業管理対象プロジェクトへ移行する際の考慮事項
Team-managed spaces and company-managed spaces are technically quite different. Here's a few things to consider when you migrate from a team-managed software space to a company-managed software space:
Board statuses: If you customized your team-managed board, you'll need to set up the same statuses in your company-managed space's workflow. Only Jira admins can create and modify statuses and workflows. More about workflows
Custom fields: If you use custom fields in your team-managed space, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed space. Custom field data will need to be recreated, otherwise it will be lost.
Work types: If you added your own work types to your team-managed space, you'll need to have a Jira admin recreate these using a work type scheme that they associate to your new company-managed space. How to configure work type schemes
Space access: Access to company-managed spaces is controlled by a permissions scheme. Only your Jira admin can update your company-managed space's permission scheme. Manage users, groups, permissions, and roles
Space and work item keys: Jira will automatically update the work item keys of migrated work items to reflect their new space. Any existing links to old keys will be automatically redirected.
Reports: Reports data won't be saved. Even though your work items will be retained, data for your space's Velocity and Burnup reports won't transfer over, and will be lost.
Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in company-managed spaces (Story points) is different to the custom field used in team-managed spaces (Story point estimate).
この内容はお役に立ちましたか?