Ask HN: Anyone use GitHub Issues at their company?

• aws-cdk

  263 11,137 9.9 TypeScript

  The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

  

I've used Jira (with integration to GitHub) at every company I've worked at. However, over the last couple of years, I noticed GitHub has been investing in their project management features.

I've seen some open source projects leverage GitHub Issues (https://github.com/aws/aws-cdk/issues and https://github.com/vercel/next.js/issues), but it just looks really unorganized compared to Jira (possible bias because I'm new to GitHub Issues).

Looking to get some thoughts on GitHub vs Jira for project management. We're a startup looking specifically at the following features: bug reporting, sprint/epic management, release management (from development, to code review, to QE verification, to release), and integration with non-engineering teams (ie, letting customer support/customer success tag issues that customers have brought up).

• Next.js

  2,041 120,572 10.0 JavaScript

  The React Framework

  

I've used Jira (with integration to GitHub) at every company I've worked at. However, over the last couple of years, I noticed GitHub has been investing in their project management features.

I've seen some open source projects leverage GitHub Issues (https://github.com/aws/aws-cdk/issues and https://github.com/vercel/next.js/issues), but it just looks really unorganized compared to Jira (possible bias because I'm new to GitHub Issues).

Looking to get some thoughts on GitHub vs Jira for project management. We're a startup looking specifically at the following features: bug reporting, sprint/epic management, release management (from development, to code review, to QE verification, to release), and integration with non-engineering teams (ie, letting customer support/customer success tag issues that customers have brought up).

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• fusionauth-issues

  22 88 7.0

  FusionAuth issue submission project

  

We do, extensively, both internally and externally. In fact, we don't have any other explicit way to order engineering work. (There's always the "inside the CTO's head" priority list, but we strive to get that into GH issues.)

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.

Suggest a related project