...
Github Entity | Description |
|---|---|
Issues | Issues can be bugs, enhancements, change requests or any other requests related to the repository |
Comments | Its a thread of discussion on a issues. Each issue can have multiple comments and each comment can have multiple attachments in it. |
Attachments | Attachments can be attached to comments only and the contents of the description are marked as first comment on the issue |
Assignee | User account to which the issue is assigned |
Projects | Github also has somethings called as projects which at first may look synonymous to projects in Jira but is is not. A single Github repository can have multiple projects and projects in github Github are similar to boards in Jira. The confusion arises due to the naming convention used over here. |
Milestones | These are similar to sprints in Jira with thier their own start and end date |
Labels | These are similar to labels in JIRA(multi select control) |
Users | Users are nothing but accounts to which issues can be assigned |
...
User account with full admin access for APIs and data download from GITHUBGithub
User account with full admin access for pushing data to JIRA
Separate system on which we can login and work(This migration involves client data so we have to use a cloud instance rather than our local machine)
Confirmation of repository/repositories to be migrated
Confirmation of users to be migrated(Client has to confirm whether the user accounts should be created in Jira or not)
Confirmation of the data to be migrated as whole(all the entities ex. repository, issues, labels, milestones ….)
Approaches for migration
Pulling data from Github - Basically there are two ways to pull the data out of
...
Github
First Way - Using the export option in the UI
...
Task | Estimation in (man hours) | Comment |
|---|---|---|
Get credentials for admin for Github from client | NA | |
Get separate VM for development work | NA | |
Installations on development environment & testing of Github account credentials | ||
Implement pulling data from Github using the api(second method) to connect and pull the data | ||
Implement the Github data processing and data transformation | ||
Implement the ability to export the transformed data in CSV format(compatible with Jira server) | ||
Testing |