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

91–100 of 213 posts

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

#91

Post by alexpovel »

smarx007 wrote: post #86
alexpovel wrote: post #81

Earlier quoted context omitted.

Agree! For fun, I had put together a GitHub bot for this purpose a while ago. It indexes all existing issues in a repo, creates embeddings and stores them in a vector DB. When a new issue is created, the bot comments with the 3 most similar, existing issues, from vector similarity. In theory, that empowers users to close their own issues without maintainer intervention, provided an existing & solved issue covers thei…

Microsoft seems to use a similar bot themselves, not sure how it is called or whether it is OSS: https://github.com/microsoft/winget-cli/issues/4765#issuecom...

Oh yeah, that looks super similar. I remember the similarity score being tricky to get useful signal out of, for the underlying model I had used back then. Similar and dissimilar issues all hovered around the 0.80 mark. But surely not hard to improve on, with larger models and possibly higher-dimension vectors.

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

#93

Post by originalvichy »

hadrien01 wrote: post #65
IshKebab wrote: post #18

Earlier quoted context omitted.

> well administrated Jira Based on my experience that doesn't exist. Hell even if it did, Jira is sooooo unbelievably slow I would still take literally anything else. Maybe even Savannah. A colleague joked that we need a "waiting for Jira" Jira task.

A well administered JIRA can be really fast. There's a reason Atlassian themselves don't use JIRA Cloud: https://jira.atlassian.com/browse

My guess is that self-hosted versions have an infinitely simpler user experience when it comes to accounts and visibility. Jira Cloud is definitely angled towards always being behind some sort of an account system, which used a real, costly backend, but the self-hosted one can get by with the local hosted IdP or an LDAP server.

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

#94

Post by badgersnake »

IshKebab wrote: post #18
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.

> well administrated Jira Based on my experience that doesn't exist. Hell even if it did, Jira is sooooo unbelievably slow I would still take literally anything else. Maybe even Savannah. A colleague joked that we need a "waiting for Jira" Jira task.

Indeed, see https://ifuckinghatejira.com/

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

#95

Post by sangeeth96 »

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 think most orgs function. I'm not sure if it'll ever try to be something more than that but I really wish it did.

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

#96

Post by IshKebab »

hadrien01 wrote: post #65
IshKebab wrote: post #18

Earlier quoted context omitted.

> well administrated Jira Based on my experience that doesn't exist. Hell even if it did, Jira is sooooo unbelievably slow I would still take literally anything else. Maybe even Savannah. A colleague joked that we need a "waiting for Jira" Jira task.

A well administered JIRA can be really fast. There's a reason Atlassian themselves don't use JIRA Cloud: https://jira.atlassian.com/browse

Huh that is much faster than Jira Cloud. How come though? Do they just hate their customers or something?

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

#97

Post by IshKebab »

dotancohen wrote: post #68
IshKebab wrote: post #18

Earlier quoted context omitted.

> well administrated Jira Based on my experience that doesn't exist. Hell even if it did, Jira is sooooo unbelievably slow I would still take literally anything else. Maybe even Savannah. A colleague joked that we need a "waiting for Jira" Jira task.

Take a look at Redmine. It's a self-hosted Ruby project manager and I love it, especially for issue dependencies.

Nobody who uses Jira is really in a position to pick anything else.

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

#98

Post by jonpurdy »

rplnt wrote: post #62
IshKebab wrote: post #18

Earlier quoted context omitted.

> well administrated Jira Based on my experience that doesn't exist. Hell even if it did, Jira is sooooo unbelievably slow I would still take literally anything else. Maybe even Savannah. A colleague joked that we need a "waiting for Jira" Jira task.

I believe Apple silicon has Jira coprocessor. It really became usable on M1 and beyond. Even the horrid UX got somehow better in the last few years (like not having 3+ different text inputs, each with different formatting behavior). My guess is since the hardware caught up with them they can now finally use it and iterate.

You jest, but I tested this and it turns out that it was JavaScript, not slow networking, that made Jira so slow for me. (I was trying to figure out how to locally cache assets to speed it up.)

The M-series single-core speeds were so much faster than Intel at the time that it was noticeably faster.

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

#99

Post by jjayj »

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…

It would be a tough sell for my org to triple our license spend on GHEC just so we can teach a bunch of folks new software.

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

#100

Post by sangeeth96 »

jjayj wrote: post #99
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…

It would be a tough sell for my org to triple our license spend on GHEC just so we can teach a bunch of folks new software.

Absolutely. They definitely can't expect to sell this to teams/orgs with non-devs without introducing separate pricing for folks who just want to read/write to projects but maybe read-only for some aspects of a repo.
Post reply on HN