generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Rabia Shaikh edited this page Aug 6, 2024
·
13 revisions
Welcome to the admin-project-board-migration wiki!
- Check to see if there are cards on the board by using this filter on the project board
if yes, do this section
is:note
- Create migration issue
- Add it to 2.01 in the Resources section of your issue
- Copy Cards
- Delete Cards
- Add labels to repo that match board names
- Add labels to issues
- Define column names (all columns from all boards)
- Add column names to the board that will be migrated
- Migrate board with most open issues
- Move other open issue to the new board, mapping them to their columns
- Make a view for each of the former project boards
- Change automation temporarily to done, and move all closed issues to the new board, change back automation
- Delete the classic boards
- Migrate board
- After migrating the old board is closed, delete the classic board
- Go to issues tab and add all issues that are not on the new project board, to the board, in the new issue approval column
- Add role views
- Make sure the new repo is linked to the new project board and the open roles board
- Make sure all old project boards are deleted
- Make sure there are no issues that are not on the project board
- Add the Migration issue to their board, in the in progress column.
- Check team's wiki to see if they have any remaining activities (such as updating their wiki)
- If no open activities, close the migration issue
- If yes open activities, add details to the action items or in a comment and move issue to questions column