Move existing tickets to the new project board

Sage-Bionetworks / rocc

Landing repository for the Registry of Open Community Challenges (ROCC)

Apache License 2.0

0 stars 0 forks source link

Move existing tickets to the new project board #30

Closed tschaffter closed 2 years ago

tschaffter commented 2 years ago

Move the existing tickets to that they are visible to the new project board.

Tips:

Identify if an existing ticket is a task/story/epic
Link tasks to stories/epics and stories to epics

jiaxinmachine88 commented 2 years ago

How mission critical is this?

Currently, the project beta exists somewhat separately from the original projects and requires manually updating each issue. I estimate it will take me about 3 hours of focused time to do this.

50 issues for the ROCC backlog and sprint boards
19 issues for RBT Backlog
100+ issues for NLP Sandbox sprint board

Additional documentation on Github Project Beta: Converting a Regular Project to Project Beta Issues/Project Beta at Repo Level

tschaffter commented 2 years ago

@jiaxinmachine88 I would say that it would be nice to have the old tickets ported to the new board by the time we start planning the next sprint, which will focus on hardening the current implementation. Hence it will be useful to have past tickets / issues reported to identify the bugs we want to fix. This basically gives us three weeks to move the tickets to the new project.

tschaffter commented 2 years ago

Done