Closed ATMiddleton closed 1 week ago
Below is some information regarding the migration.
https://dsva.slack.com/archives/C07H8R1PTGX/p1730306012793879
All Zen Hub issues have been successfully migrated to Git Hub. Veteran Support will use Git Hub going forward.
Issue Description
Migration Scope Boards: Migrate ZenHub boards to GitHub Projects or other organizational tools. Epics: Translate ZenHub epics into GitHub issues or custom fields in GitHub Projects. Pipelines: Map ZenHub pipelines to GitHub project columns or workflows. Labels: Transfer all custom labels and color coding from ZenHub to GitHub. Milestones: Migrate milestones and ensure due dates and connections to issues are preserved. Reports: Set up alternative reporting methods using GitHub’s built-in tools or external integrations (if necessary).
As a product manager, I want all ZenHub issues and epics to be migrated to GitHub Projects without losing any data, so that I can continue managing my tasks and priorities without interruption.
Tasks
Acceptance Criteria
[x] Issues retain their connections to epics after the migration.
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)