Live data from Hacker News

GitHub introduces sub-issues, issue types and advanced search

github.blog

141–150 of 213 posts

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

#141

A few jobs back I got “promoted” (honestly I didn’t want it but I digress) to an EM. First thing I did was ditch Jira for GH issues. I was hailed as a hero for it. Unfortunately it ended up being a disaster and we had to switch back a year or so later. These were some of the missing features so pretty exciting.

You should write Cliff's notes for the Odyssey. What an epic summary.

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

#142
post #62

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.

"Apple silicon has Jira coprocessor" time to retire to the country and raise chickens.

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

#143

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 do at Grafana - it's mostly all public so you can go look at the mess of trying to run jira boards for however many teams out of one repo https://github.com/orgs/grafana/projects. It's a mixed bag, but Github's been building out Issues and Projects a lot in the last few years that's really improved things.

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

#144
post #138

Earlier quoted context omitted.

I suspect it's more to do with issue management isn't their core product so doesn't get the same attention an issue management system would give it.

Wait if it's not their core product, what is ? GitHub is, at its core, a file/history browser + issue management system + merge request system built around Git. There's not that much to it other than issue management.

It's core product is git hosting, you use it to host your git repositories. You use features such as Pull Requests to power how you merge within your git repositories. If the issue system isn't working it's not a big deal, but if we can't use git it's a massive deal. It's all in the name GIThub

Most companies don't use GitHub's issue management system they use issue management tools such as JIRA, Trello, etc. Issue management, project management, CI/Actions, wiki, discussions, etc are all nice to haves and are probably more aimed at the open source projects that are used as a marketing tool.

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

#145

Earlier quoted context omitted.

This is fiction considering Microsoft is extensively using Azure DevOps internally and is still developing it. Moving projects away from it and to GitHub is impossible because they're incredibly far from having feature parity.

Feature parity is probably not required as long as the different teams are able to adapt their workflow to GitHub's approach. Anecdotally, every employee from Microsoft I've talk to about this point during the last two years keep telling me that ADO is over.

Feature parity is absolutely required. We are ADO customer because A) Inertia and B) GH Actions is nowhere close to features of ADO Pipelines.

Every conversation we have with Microsoft about our ADO -> GH migration is either get GH to feature party or if you force us to migrate, we will evaluate ALL our options.

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

#147
I wish they would build features to defend against those near-spam type comments where someone is lazy and appends their clearly unrelated issue onto an existing one that maybe shares a few keywords but nothing substantive.

It's not quite spam: there's often a real person behind it with a real issue but they need a (metaphorical) slap before they muddy the waters and disturb countless people already in the conversation.

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

#148

I wish they would build features to defend against those near-spam type comments where someone is lazy and appends their clearly unrelated issue onto an existing one that maybe shares a few keywords but nothing substantive. It's not quite spam: there's often a real person behind it with a real issue but they need a (metaphorical) slap before they muddy the waters and disturb countless people already in the conversati…

This would be worthwhile for the individuals too - you often find a recurring pattern with all / most of their raised issues and with basic guidance they might up their game (or give up)

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

#149
post #78
post #73

Earlier quoted context omitted.

GitHub doesn’t have ads and makes its money off of enterprise subscriptions (and Copilot), so I don’t think “engagement” is a very important metric for them.

To the company, no. But to people trying to get a promotion/bigger budgets by proving the features they work on are getting a lot of usage, plausible.

> To the company, no.

Why not? Companies love to boast about MAUs and similar metrics (even if completely bogus), it has good effect on stock prices.

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

#150

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 do. We're an agency so there's probably 60 odd repos on GitHub each with a project attached, a lot of non-tech people (even clients) using the issues and boards. Nobody has complained, though every now and then I've looked around for something else, but for me the number one priority is that the code and issues are in perfect sync with each other - much harder with a 3rd party tracker.
Post reply on HN