Yes, I started using it 6 months ago. We only have one team of 5 developers. Compared to Jira, it is not gut-wrenching terrible. My employer's project manage

Yes, I started using it 6 months ago. We only have one team of 5 developers. Compared to Jira, it is not gut-wrenching terrible. My employer's project manager left the month after I started, so I took over his overview. I switched from Jira to GitHub Projects because I value my life as a developer. It's not as feature rich, but that's a feature. The integration with PRs and commits is top class. Projects can span multiple repositories, which is neat. We are mostly mono-repo, but we do have one active project using a different set of technologies. I have one long-lived project for getting our main product ready, containing several milestones, some of which have deadlines yet to be determined, some deadlines stretching 6 months into delivery. I use the kanban board for keeping track of what my colleagues are working on, and for measuring how much is left. I don't use the roadmap feature, because my employer has a time estimation problem right now, but it looks very neat. I use a "tracking issue" label that just lists other issues. For example, a tracking issue for a particular customer. I really like how doing "- #123" in an issue or PR expands that into the title and an icon indicating if it was open or closed. This is just standard GitHub functionality, but it's super. Sometimes tracking issues are created from doing a customer integration test, where a failed test is converted into a task. But until they're a separate issue, they're just a bullet point in the tracking issue. I'd like to be able to export an interactive overview of a subset of issues for customers to look at between meetings (which is possible to make with GitHub's API). But it's not strictly necessary, as screenshares / screendumps of the issue tracker is typically fine.