Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub introduces sub-issues, issue types and advanced search

github.blog

Post reply on HN
Print view View original

101–110 of 213 posts

Re: GitHub introduces sub-issues, issue types and advanced search

#101

Post by jonpurdy »

decide1000 wrote: post #12

I am not sure if I am going to like this feature. I miss the simplicity. Guess those times re over.

It is less simple, but nowhere Jira-level, and yet still more useful (for my team and I).

We've been using GH Projects at my current org and program for two years. The one feature I wish it had was nested issues.

In Jira, you had Epic > Task > Sub-task and that's it. With GH, you can just have issue > issue > issue (insert "it's turtles/issues all the day down meme"). So it's more powerful, but can be ignored by folks who don't want to do this.

Re: GitHub introduces sub-issues, issue types and advanced search

#102

Post by renegade-otter »

decide1000 wrote: post #12

I am not sure if I am going to like this feature. I miss the simplicity. Guess those times re over.

GitHub is free for most people, so they are only beholden to large organizations and their feature requests. This is how it seems now - a feature creep by committee. It's getting more and more bloated and unwieldy, sort of like what happened to AWS.

Re: GitHub introduces sub-issues, issue types and advanced search

#103

Post by sangeeth96 »

Calzifer wrote: post #9

Great, a few more decades and it might become a usable bugtracker. What's next on the list? Maybe priority/severity or status/resolution? I helped on a quite large open source project for some time and loved working with Bugzilla. The announced switch to Github for that project was one reason I lost interest. I even prefer to work with a well administrated(!) Jira over Github issues.

I really feel like GH needs to spin out Projects into a more dedicated, funded team while still maintaining a close sync in order for it to become more viable/interesting. Besides allowing it to grow faster and better, that should also allow for non-dev seat pricing.

Re: GitHub introduces sub-issues, issue types and advanced search

#106

Post by acjohnson55 »

sangeeth96 wrote: post #95

I'm curious if there are folks here who work at for-profit orgs who use GitHub projects as their sole issue tracker for the entire org. How do you do it and what are the common pain points? Do you couple it with other issue trackers/project management tools like Jira? If so—why? I still feel GH Projects is solely aimed at OSS or dev-centric or dev-only orgs and doesn't cater to teams with non-devs, which is how I thi…

We did at my previous employer (https://www.ourbranch.com/) in our data org. I can't totally remember, I'm pretty sure the engineering org did, too. It definitely is lacking in some of the advanced features you get with a Jira, but it was fine. I was surprised by how powerful GitHub Projects is. We also built out extra reporting for it in our data warehouse, using Fivetran for ELT.

Re: GitHub introduces sub-issues, issue types and advanced search

#107

Post by paulryanrogers »

the_duke wrote: post #104

Slowly inching towards something usable for companies / large projects... One big thing missing is resolution status for issues, like "cancelled", "complete", ...

You can close as complete (default) or unplanned today. It's called the 'reason'.

Re: GitHub introduces sub-issues, issue types and advanced search

#108

Post by paulryanrogers »

jxi wrote: post #90

Strange that issue types is only available if your repository is part of an organization. Why is this not configurable at the repository level?

To upsell? To maintain consistency among repos? To facilitate use among GH Projects?

Re: GitHub introduces sub-issues, issue types and advanced search

#109

Post by paulryanrogers »

replete wrote: post #80
donatj wrote: post #72

This seems... unneeded bloat? I guess there are some obsessive organizers out there, but a markdown checklist of steps - potentially with links to other tickets seems like all you need. If you're going to improve something improve code review! Let me comment on and suggest diffs to lines the author did not touch. Like half the time I am reviewing code it is "Hey, you refactored this but you missed a usage in this oth…

A lot of this will seem trivial if you haven't used Github for an organization's management of issues. This also lets you start off with a markdown checklist, and convert items to sub-issues.

> This also lets you start off with a markdown checklist, and convert items to sub-issues.

Wasn't that already possible with Tasklists? We did it using "- [ ] description", then clicking the covert-to-issue hover option.

Re: GitHub introduces sub-issues, issue types and advanced search

#110

Post by grajaganDev »

hamandcheese wrote: post #48

A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.

Meta and Google have this in their internal systems.
Post reply on HN