...
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
...
High Level Tasks
Sl No | Task | Estimation in (man hours) | Comment |
---|---|---|---|
1 | Get credentials for admin for Github from client & Jira Access | NA | Action required from Client it is required to export the attachment data |
2 | Get separate VM for development workNA | Action required from Client | |
3 | There should be a mapping document to show which field in Github map to which field Jira | Empyra team to create the mapping and get confirmation from the customer | |
4 | Installations on development environment & testing of Github account credentials | Yes we have | |
5 | There should be a way for the utility to pull data from Github | Yes we have | |
6 | There should be a way for the utility to transform the data from Github format to Jira understandable format | Analysis is done. Transformation to be worked upon. | |
7 | There should be a way for the utility to export the transformed data to CSV format understandable by JIRA | Action from Empyra team | |
8 | There should be a way for the utility to generate report of data pulled from Github | Action from Empyra team | |
9 | There should be a way for the utility to generate report of data exported to CSV format | Action from Empyra team | |
10 | There should be a way for the utility to check the data in Jira cloud using api calls and generate report of data exported | Action from Empyra team | |
11 | Testing | Action from Empyra team |
...
Task | Details | Aim | Status |
---|---|---|---|
Migrate : 10 Closed and 10 Open issues Migrate: 5 Milestones and 5 project with attachments | In Gihub, create two four milestones and add few issues under each | To check if we can create closed sprints in Jira or not | |
Migrate User data | In Github invite some users to join the organization | To check if we have enough information to create a user in Jira from Github | |
Migrate Comments | In Github create comments under different issues. | To check if we can migrate the comments under a project and a issue or not | |
Migrate Attachments | In github create an attachment, Migrate this attachment to JIRA | To check if we can migrate the attachment to proper issue or not | |
Check the release version | Try to migrate releases from Github to Jira | To see if we can migrate releases data or not |
Stories & Estimations
# | Story | Tasks | Estimation(in man hours) |
---|---|---|---|
1 | Utility should be able to pull data from Github | ||
Utility should be able to pull api data from Github | 8 | ||
Utility should be able to download the migration data | 8 | ||
Utility should be able to save the data locally to the hard drive | 3 | ||
Utility should be able to join the organization migration(attachment) data to data pulled from api | 8 | ||
Utility should be able to generate the report based on data pulled from Github | 8 | ||
2 | Utility should be able to transform the data in JIRA compatible format | ||
Utility should be able to read and transform the data into CSV format compatible with JIRA | 28 | ||
Utility should be able to generate the report of the transformed data | 6 | ||
3 | Configure the test JIRA server instance to emulate the cloud | ||
Create users in the jira instance | 2 | ||
Create all projects with same name as labels in Github and custom fields | 2 | ||
Person should be able to import the data in Jira server | 0.1 | ||
Utility should be able to generate a report to validate the data in JIRA server against the data imported in CSV format | 8 | ||
Validate the migrated data | 1 | ||
4 | Import the transformed data into Jira cloud | ||
Person should be able to import the data in JIRA cloud | 0.1 | ||
Validate the migrated data | 2 | ||
Total | 84.2 |