Re:Ask HN: Anyone use GitHub Issues at their company?
by cfcosta on Tuesday March 29, 2022 @11:21AM
(#30843780)
Kinda unrelated, but I actually had never thought about doing a "reverse open source" like this, with open development but closed source.
Having worked in strictly open products in the past, there's a lot to be gained having your issue tracker public, and letting anyone interested joining the discussion.
It's not like you are doing military stuff or anything that needs to be that secretive, and if there is something secretive, you can just use another project.
Re:Ask HN: Anyone use GitHub Issues at their company?
by mooreds on Tuesday March 29, 2022 @12:59PM
(#30845251)
Yup. The value from people being able to make and find feature requests and vote on them far outweigh the value of a "secret roadmap".
We've definitely guided large chunks of our development effort from this issues list.
https://github.com/fusionauth/fusionauth-issues/issues is our main external facing repo. We use it:
* to track issues. Every code change should tie back to an issue in this repo.
* to get feedback from the community. People can upvote issues that are important to them.
* to take input from the community. If someone wants a feature added or a bug fixed, we ask them to file an issue. This is a desired bit of friction (if you can't be bothered to file an issue, then you probably don't care that much).
* to expose the near term roadmap to customers and community members (we do this using milestones)
* to expose our decision making and prioritization process. We've had customers say they loved that about our product. The product is not open source, but the development process is as transparent as we can make it (see https://github.com/FusionAuth/fusionauth-issues/issues/1577 for example).
It's great for all those things. On to your concerns:
* bug reporting: yes, but make sure you use templates
* sprint/epic management: okay for that. Not easy to tie bugs together in any structured way (we use a 'related bugs' section of the issue description, but that depends on frail humans to keep it up to date)
* release management (from development, to code review, to QE verification, to release): less familiar with this, I know there is a kanban view that we've used. Milestones are useful here.
* integration with non-engineering teams (ie, letting customer support/customer success tag issues that customers have brought up): as long as they are GH knowledgeable, it'll work.
From my limited jira experience, it's much more powerful when you have teams of teams and need reporting and customization. But for a team our size (<10 engineers), GH issues has been great.