Versions Compared

Old Version 25

changes.mady.by.user improvekit

Saved on

compared with

New Version 26

changes.mady.by.user improvekit

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Suggested migration steps

Previous to run the migration, you should do the following in your JIRA 2 (destination):
  • Create manually metadata that can not be created with the JIRA REST API. With metadata I mean data other than issues, which are referenced by issues. Not all of this data can be created through web services. When creating an issue, it is necessary to some extent that there are workflow data, screens, fields, custom field configuration, and permissions for it to be successful. This data is maintained in JIRA with the option to manage the project.
  • Priorities
  • Resolutions
  • Configure Custom fields (see also custom fields options). CUSTOM FIELDS MUST HAVE AN UNIQUE NAME
  • Screen must be include the following fields: components, environment, versions, duedate, reporter, fixVersions, assignee, timetracking, labels, and needed custom fields. From version 1.1.0 is autoconfigured by the plugin
  • Issue type schemes used by the projects must include issue types referenced by imported issues. From version 1.1.0 is autoconfigured by the plugin (only server targets)
  • Permission schemes (grants for create/update/transition/worklog/comment)
  • Workflows with a Done terminal status for resolved issues
  • Configure users (inactive users will be migrated as admin, see also default user option


After migration, as final step, you should complete each project issue's schemes as needed


Info
  • Issuetypes are not case sensitive
  • Migrated issues can have different issue key in destination depending on the order of creation and the initial numvalue of each project key
  • Only custom fields of built-in types are migrated 
  • All resolved issues are closed using a given transition (Done) from the initial status that sets the Resolution. After migration you can discard this transition
  • Only issue field's not hidden in project field configuration are migrated
  • Migration JIRA user need to be administrator with  Browse grant in all source projects, and with Create/Edit issues, Modify Reporter, etc. permissions on destination migrated projects
  • Option export issues always inserts and/or updates (does not omit records)
  • File attachments are located in your Jira Home, folder  /import/attachments. You can copy the attachments in a folder for each issue manually or with the update existing information option make the plugin download them for you


...