Versions Compared

Key

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

...

Way to pull data

Using Organization data export and API

Details

We can use best of the above two approaches to get the work done. In this approach we can export the organization data using the manual exports (or organization migration api) to get hold of the attachments attached to issues(we cannot get attachments using apis) and then fetch the other information about the organization like repositories, issues, comments, labels, milstonesmilestones, releases, projects etc using the relevant github apis

Pros

We can download all the data for an organization using this approach

Cons

Export option in github UI for any user account does not give the ability to export organization data. It only allows us to download the data which is belongs to that account and not to any organization.
We may have to use Github’s Async organization migration API to get around this problem

High level steps for pulling the data

  • Export the organization data using Either UI or organization migration api (for attachments)
    POST /orgs/:org/migrations - to start the process of generating the organization data
    GET /orgs/:org/migrations/:migrationId - to check the status of migration process
    GET /orgs/:org/migrations/:migrationId/archive - to download the compressed file with organization data and attachments

  • Us the Github api to pull the data for other entities(repositories, issues, comments, projects, milestones, labels)

...

Data can be imported in Jira cloud using the CSV format. We can refer to the following link to generate the data in CSV format for both data and attachments.
Jira server - https://confluence.atlassian.com/adminjiraserver087/importing-data-from-csv-998872306.html
Jira Cloud - https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

Note : For importing attachments it is required to have the attachment data available over http/https so that it is accessible to Jira server/Cloud directly

Task Breakdown and Estimation

...