Jira Cloud Migration Assistant로 마이그레이션되는 항목

Jira Software project data

• Issue rank

• Epics (epic link)

  • Epic name

  • Epic color

  • Epic link

  • Epic status

• Issue history (including some custom fields)

  • Epic Name

  • Epic Color

  • Epic Link

  • Epic Status

  • Issue rank

  • Original Estimate

  • Remaining Estimate

  • Flagged

  • Components

  • Environment

• Sprints

• Versions (affects versions, Fix versions)

• Filters associated with boards being migrated

• Boards connected to only one project that is being migrated

• Jira Software Boards - connected to projects selected in the migration (boards linked to more than one project will not be migrated)

  • Boards

    • Name

    • Administrators

    • Filter & permissions

    • Location

  • Advanced board settings

    • Column names & status mapping

    • Quick filters

    • Swimlanes

    • Sprint permissions

    • Card colors

    • Time statistic / estimation

Jira Service Management project data

• Jira Service Management projects

• All users including agents

• All groups

• All customers

• Request type

• Request type groups

• Project entities

• Custom Fields

  • Customer organization

  • Approval

  • SLAs

• Project Settings

  • Automation rules

  • Customer notification template

  • Portal settings

  • Calendar

  • Workflow

  • Language support settings

  • Customer satisfaction settings

  • Reports

• Queue

Jira Work Management (formerly Jira Core) project data

Note: These entities are also part of Jira Software and Jira Service Management.

• Project details:

  • Name

  • Key

  • Project type

  • Project category

  • Description

  • Project lead

  • Default assignee

• Project roles

• Issue types

• Issue type scheme

  • Default issue type

• Issue type screen scheme

• Workflows scheme

• Field configuration scheme

• Workflows - basic links to the correctly migrated workflow scheme with status and transitions

• Workflow functions

  • Full list of workflow rules that are migrated

• Screens schemes

• Screens

  • Tabs

• Status category

• Permission schemes

• Issue security

Issue data

• Summary

• Description

• Issue type

• Issue number

• Status

• Priority

• Resolution

• Labels

• Creator

• Reporter

• Assignee

• Due date

• Subtasks

• Some custom fields

  • Text

  • Date

  • Number

  • Time

  • Labels

  • Select List (single choice, multiple choice, cascading select)

  • Checkbox

  • User Picker (single/multiple)

  • Project picker (single project)

  • Group custom fields

  • Multi-line text

  • Radio button

  • Environment

  • URL

• @mentions

• Watchers/ Votes

• Issue links (including link types)

• Attachments

• Comments

• Comments with security

• Story points

• Time spent

• Issue history

• Issue work log

• Issue key history

Users and groups from active directories

• Jira Work Management and Jira Software users, and Jira Service Management agents

• Deleted users from server are migrated as “Former user”. Only deleted users connected to the projects being migrated will be created in cloud

• All groups in active directories

• Users managed by external directories

App data

• Marketplace Partners (also known as App vendors) need to have built an automated migration path to allow JCMA to migrate app data.
  See a list of Jira apps with migration paths.

Other project types

• Archived projects

Project setup

• Custom field language translations

• Workflow functions

  • Properties

  • Triggers

• Notification schemes - projects are added to the default schemes in cloud

• Mail handlers

• Project avatars

• Links to issues or entities that are not migrated

Jira global entities and permissions

• Global permissions

• General configuration (timezone, language, etc)

• Dashboards

• Cross-project boards

• Boards not connected to the projects being migrated

• Boards that belong to inactive users

• Filters on boards that are not migrated

• Confluence links

• Webhooks

Users and groups

• Users and groups from inactive directories - make directories active to migrate them

Specific app data

• Advanced Roadmaps (formerly Portfolio for Jira) migration is in the roadmap.

• App data of the ‘Automation for Jira’ app is not included in the migration.

User profiles

• User avatars. Users will need to update their avatars after migrating

• Passwords. Unless you've set up SSO, users will need to reset their passwords after migrating

• Timezones. Timezone information on a per-user profile will be lost

Other issue types

• Archived issue