[buro9]

Grafana Labs is using Github Projects and Issues for ~500 engineers that we have and the extended FOSS community contributing to projects like Grafana, Loki, Mimir, Tempo, and Pyroscope.

It is possible to do, I ack that we're below your 1k engineers threshold (though the OSS side is way above), but the problem isn't Github it's whether you (as an org) dictate a single SDLC that you enforce via a tool and as we aren't doing that and we're not yet encountering difficulties (beyond culture shock when people onboard and can't find what they're used to elsewhere, being Jira). By working with autonomy, and in fact embracing OSS and the community (meaning we can't hide info in internal Jira instances), it's easy to avoid Jira.

That's the rub though, many places do not want to give engineers autonomy like this.