Use of this repository is for tracking Sustainment Team Issues. It is used to account for the Sustainment Team's work that is not attached to a specific digital service.
0
stars
0
forks
source link
Review Python Script in Preparation to move from ZenHub to GitHub Projects #5
Describe the task
Review Python script and assist in the migration of Sustainment team's ZenHub space into GitHub Projects.
Purpose
To automate the migration instead of doing it manually.
Acceptance Criteria
[ ] Review the script and determine if any code changes needed to migrate tickets to the new Sustainment Team board.
[ ] Review the script to determine code needed to migrate closed tickets (see Additional Context for more info)
[ ] Check if all ZenHub tickets have an ZenHub project ID (see Additional Context note from Conor about migrating bcgov and bcgov-c org tickets)
[ ] Request back-up of Sustainment Team's ZenHub board - should be done before migration
[ ] Migrate from ZenHub to GitHub Projects
Additional Context
Summary from DDS ZenHub chat re closed tickets:
Apparently closed tickets aren't being migrated. Conor's team didn't import closed tickets and had this to say: "one probably could though. Would require a dev to check out the Github API. I think with that limit you can archive tickets to mitigate the 1200 limit."
FOR DISCUSSION WITH THE TEAM: Do we even need to migrate over closed tickets? We could do this manually if needed?
With regard to migrating both bcgov and bcgov-c org tickets, here's what Conor had to say:
"The migration script will (with some prodding) map all issues under [zenhub project id] to [github project id] . So assuming the bcgov and bcgov-c have their own unique zenhub projects, you should in theory be able to tell the script to migrate both to the same github project. The script would have to be run once for each zenhub board for bcgov and bcgov-c, haven't tested it though."
Conor B has agreed to answer questions for whomever takes this ticket on. Suggested Office Hours session could be used for questions/discussion.
Jan 12/24 - In speaking with Conor, the Python script moves everything from ZenHub over to GitHub Projects. Therefore, the Sustainment Team's ZenHub backup files (JSON) located here are back-up only and aren't needed for the script to run.
Describe the task Review Python script and assist in the migration of Sustainment team's ZenHub space into GitHub Projects.
Purpose To automate the migration instead of doing it manually.
Acceptance Criteria
Additional Context Summary from DDS ZenHub chat re closed tickets: Apparently closed tickets aren't being migrated. Conor's team didn't import closed tickets and had this to say: "one probably could though. Would require a dev to check out the Github API. I think with that limit you can archive tickets to mitigate the 1200 limit."
FOR DISCUSSION WITH THE TEAM: Do we even need to migrate over closed tickets? We could do this manually if needed?
With regard to migrating both bcgov and bcgov-c org tickets, here's what Conor had to say: "The migration script will (with some prodding) map all issues under [zenhub project id] to [github project id] . So assuming the bcgov and bcgov-c have their own unique zenhub projects, you should in theory be able to tell the script to migrate both to the same github project. The script would have to be run once for each zenhub board for bcgov and bcgov-c, haven't tested it though."
Conor B has agreed to answer questions for whomever takes this ticket on. Suggested Office Hours session could be used for questions/discussion.
The information below is from the ZenHub Migration Information Package
"If you have access to a developer, there are scripts available to move some of the ZenHub-stored data into GitHub Projects.
https://pypi.org/project/projectsmigrator/ (Use Conor Brady's fork)
How to migrate from ZenHub to GitHub Projects (beta) · GitHub (Not tried/tested)"
Jan 12/24 - In speaking with Conor, the Python script moves everything from ZenHub over to GitHub Projects. Therefore, the Sustainment Team's ZenHub backup files (JSON) located here are back-up only and aren't needed for the script to run.