...
We have to pull the data out of Github and push it to Jira. We have identified the entities from Github which needs to be migrated to Jira. They are as follows,
Sl No# | Github Entity | Description |
|---|---|---|
1 | Issues | Issues can be bugs, enhancements, change requests or any other requests related to the repository |
2 | Comments | Its a thread of discussion on a issues. Each issue can have multiple comments and each comment can have multiple attachments in it. |
3 | Attachments | Attachments can be attached to comments only and the contents of the description are marked as first comment on the issue |
4 | Assignee | User account to which the issue is assigned |
5 | 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 are similar to boards in Jira. The confusion may arise due to the naming convention used over here. |
6 | Milestones | These are similar to sprints in Jira with their own start and end date |
7 | Labels | These are similar to labels in JIRA(multi select control) |
8 | Users | Users are nothing but accounts to which issues can be assigned |
...
Current State of the Github Account
Sl No# | Entity | Count | Details |
|---|---|---|---|
1 | Repository | 1 | Name - SiftScience/code |
2 | Issues | 16,801 | 2861(Open Issues), 13940 (Closed Issues) |
3 | Projects | 8 | Set up Digicert access for sre@, |
4 | Milestones | 174 | 51(open), 123(closed) |
5 | Labels | 116 | |
6 | Users | 31 | Users with “sift” in their username |
...