search

ocadotechnology / codeforlife-portal

The portal code for Code for Life
Other
49 stars 63 forks source link

GitHub project management #2316

Closed SKairinos closed 1 week ago

SKairinos commented 3 weeks ago

We would like to switch from using ZenHub to using GitHub Projects as our project management tool. Before we make the switch, we want to ensure we're not loosing any features we require.

Currently, we use ZenHub to manage our GitHub issues - it gives us a nice overview of the issues. Under the hood, each issue on the ZenHub board is synced to a GitHub Issue in its respective repo.

The features that we use in ZenHub and would like to continue using in GitHub are:

  1. KanBan boards
  2. Roadmaps
  3. Workflows - We should be able to pull issues from multiple repos into one board.
  4. Epics (see this thread)

Please create your own github repos with dummy issues to test to what extent GitHub supports these ZenHub features.

andymales2 commented 2 weeks ago

I'm looking at this now, trying out a few things on some local repos and projects to see what GitHub can do compared to ZenHub.

andymales2 commented 2 weeks ago

I've done some analysis on GitHub's Projects. I'm totally new to GitHub so there may be more to be uncovered, plus I have only added a few test files so haven't tested any workflows, just created some test projects in my personal account. Here's my analysis doc on it: GitHub Projects

lauracumming commented 1 week ago

I think from the findings, it looks like a move to Github projects could be feasible. However, I suggest we wait another 4-6 months to allow new features to be released, Kurono to be taken down and any superfluous repos archived, we move to AWS. Then once there, we reassess.

In the meantime, I will use Miro for my own workflow, but when we do sprint panning as a team, we will try to only use Zenhub to plan and prioritise. This means I will need more time in each sprint to do this.