I've been doing this for all of my personal projects for a few years now and it works really well for me.
GitHub Issues has exactly the set of features that I need. I'm confident I understand 100% of the functionality that it offers, and I use all of that functionality.
(The "GitHub Projects" stuff hasn't stuck for me, but that's presented as an optional layer on top of issues so it's easy to ignore it.)
I also love how programmable Issues are. The APIs (both REST and GraphQL) are easy to use, and the options for automation using GitHub Actions are exciting, though I've not done much with them yet.
I also like having an exit plan for this kind of tool, and the API means I can easily get all of my issues data out again. I wrote a tool called github-to-sqlite which exports my data to SQLite and I use it to build a SQLite database that brings together data from many of my projects so I can search and query it in one place - demo here: https://github-to-sqlite.dogsheep.net/
GitHub Issues has exactly the set of features that I need. I'm confident I understand 100% of the functionality that it offers, and I use all of that functionality.
(The "GitHub Projects" stuff hasn't stuck for me, but that's presented as an optional layer on top of issues so it's easy to ignore it.)
I also love how programmable Issues are. The APIs (both REST and GraphQL) are easy to use, and the options for automation using GitHub Actions are exciting, though I've not done much with them yet.
I also like having an exit plan for this kind of tool, and the API means I can easily get all of my issues data out again. I wrote a tool called github-to-sqlite which exports my data to SQLite and I use it to build a SQLite database that brings together data from many of my projects so I can search and query it in one place - demo here: https://github-to-sqlite.dogsheep.net/