Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Include Page
RMC:Header
RMC:Header

Topics

Table of Contents
none
minLevel1style
maxLevel6
include
outlinefalse
indent
styledefault
excludeTopics
typelist
class
printabletrue

Assumptions and considerations

...

Special permissions

Recreate special permissions manually on both global and project levels, such as:

...

The following lookup tables are to be created:

  1. Proejct Project ID DC  -> Project ID Cloud 

  2. Version ID DC -> Version ID on Cloud 

  3. Board ID DC -> Board ID Cloud

...

  1. In order to get comments, for each Package ID, execute the request:

    1. GET https://<your_jira_url>/rest/release-management/1.0/release/comment/<release_id>/comments

    2. Get the response and store comment values for each package. All other fields are not needed

...

  1. In order to get Milestones, for each Package ID, execute the request:

    1. GET https://<your_jira_url>/rest/release-management/1.0/release/<package_id>/milestone

    2. As a result, the collection of milestones will be received

    3. For each milestone store:

      1. Name

      2. Description 

      3. Date

      4. Archived flag

      5. Archived Date

      6. Collection of triggers

...

Please use all entitled IDs from look-up tables to match DC IDs with Cloud IDs (for instance mapping of Cloumn Column ID)

For each package in the data set execute:

POST https://rmcloud-prd.releasemanagement.app/api/1/package

Payload:

Code Block
{
   "boardId":"<board_id>",
   "name":"<Name>",
   "description":"Migrated package Description",
   "versionIds":[
      "<version_id_from_lookup>",
      "<version_id_from_lookup>",
      "<version_id_from_lookup>"
   ],
   "virtualVersionIds":[
   ],
   "columnId":"<column_id_from_look_up>",
   "synchronize":false,
   "synchronizeParams":{
      "name":true,
      "description":true,
      "startDate":true,
      "releaseDate":true
   },
   "startDate":"<start_date>",
   "releaseDate":"<end_date>"
}

...

For newly created packages execute the request:

POST https://rmcloud-prd.releasemanagement.app/api/1/tag/package/<package_id>

Payload:

Code Block
["<add_tag_coma_separated>","<add_tag_coma_separated>"]

...

For each comment in the dataset execute the request:

POST https://rmcloud-prd.releasemanagement.app/api/1/package/<package_id>/comment

Payload:

Code Block
{"content":"<comment text>"}

...

For each milestone in the dataset please execute the requests

  1. Create Milestone:

POST https://rmcloud-prd.releasemanagement.app/api/1/package/<package_id>/milestone

Payload:

Code Block
{
   "boardId":"<baored_id>",
   "name":"<Milestone_name>",
   "date":"<milestone_name>",
   "packageId":"<package_id>"
}

...

  1. Update milestone with extra data

Execute request: 

PUT https://rmcloud-prd.releasemanagement.app/api/1/package/milestone/<milestone_id>

Payloads:

Update description:

...

For each comment in the dataset execute the request:

POST https://rmcloud-prd.releasemanagement.app/api/1/board/<baord_id>/version/<version_id>/comment

Payload:

Code Block
{"content":"<comment text>"}

...

For each milestone in the dataset please execute the requests

  1. Create Milestone:

POST https://rmcloud-prd.releasemanagement.app/api/1/version/<vesion_id>/milestone

Payload:

Code Block
{
   "boardId":"<board_id>",
   "name":"<name>",
   "date":"<milestone_date>",
   "versionType":0
}

...

  1. Update milestone with extra data

Execute request: 

PUT https://rmcloud-prd.releasemanagement.app/api/1/version/milestone/<milestone_id>

Payloads:

Update description:

...

Info

Multiple properties could be changed in a single request.

Include Page
RMC:Footer
RMC:Footer