DEV Community

Discussion on: For those who make use of GitHub Projects—What's your process?

Collapse
 
thibmaek profile image
Thibault Maekelbergh

We're currently trying this out across a team of PO's, designers & devs for an open source application: github.com/inthepocket/white-label...

Since this one of our first semi-large OSS apps, we're trying to use Github Projects as a substitute for Jira:

  • Todo 👉🏻In Progress 👉🏻 In Review 👉🏻 Done. These auto update for the todo & done columns.
  • Assign like you would in Jira
  • Labels as pseudo story points
  • Planning to use Projects in conjunction with milestones to link them to an actual version goal and use Github tag releases per new version.

I like how where the above is going, but overall it's still very minimal and creating 'tickets' out of the projects board directly is still a bit cumbersome since they need to be converted to issues first and then open the actual issue to do all the labeling & assigning.

Personally, I mostly use it as a road map or once (before I used Things.app) I used it as my personal todo tool to use Kanban for non-dev related tasks. But that was during the early phase when it came out, and it wasn't as mature back then as it is now.

Collapse
 
dpashutskii profile image
Dmitrii Pashutskii • Edited

Agreed with the story above. I use GitHub projects the same way as I use all similar tools (Trello for everything, Jira for office job tasks) in Scrum style.
It's for example, my last project with additional column For review for waiting for a review from a client.
github flow