Live data from Hacker News

New GitHub Issues Beta

github.com

91–100 of 223 posts

Re: New GitHub Issues Beta

#92
post #9

I wonder how tense things are over at Atlassian right now. Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them.

I always got the sense that Jira is only universally hated by people who use it but have absolutely no say in whether they have to use it.

Having no say in having to use any piece of software is a straightforward way to make people hate it.

Re: New GitHub Issues Beta

#93
post #9

I wonder how tense things are over at Atlassian right now. Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them.

I don't think that will happen just because the real problem is how software like this is usually bought. They'll ask 20 departments for their (heavily conflicting) requirements and then chose the one that ticks the most boxes without paying any attention to usability, which automatically means jira. To compete with that you'd have to do the same thing as them, at which point your tool end up just as unusable. (also see: gitlab)

Re: New GitHub Issues Beta

#94

This doesn't seem to have the one feature I want most, which is the ability to track the status of projects and milestones that span multiple repositories. Anyone know if this is there and they didn't mention it, or is on the roadmap?

Yes, this is one of the main scenarios we are enabling in the Fall. Project tables and custom fields are already cross-repo enabled in the beta.

Oh sweet! This is great news, thank you.

Re: New GitHub Issues Beta

#95

Earlier quoted context omitted.

This is so close to reality it really hurts - like a good The Onion article... excellent satire. Powerful tools are flexible enough to be used correctly by knowledgeable people and help people become knowledgeable. Badly designed tools are tools which don't help people become knowledgeable and don't prevent unknowledgeable people from harming themselves or others using them. Atlassian tools, like JIRA, are almost alw…

Right, it turns into a political game instead of a powerful and useful tool. We have no control over how we use JIRA. It's all prescribed by someone and we don't even know who or how to reach out to them. Even the middle managers don't know how JIRA is being prescribed. They go one step worse and make Tableau dashboards from JIRA to track their own metrics that are so bad it's just... like The Office. We play the gam…

This is super common, and it's one reason why I have always volunteered (even though it sucks) to be the Jira Person. I'm experienced with it and have a good handle on how not to make it a big giant workflow mess, and I can then make sure that, by not being shy about who's running it and managing it, that feedback goes somewhere actionable.

Re: New GitHub Issues Beta

#96
> Automatically add issues to a project,

That was the one thing I actually absolutely needed missing from current "Projects". Seems like such a simple basic thing, but the fact that I couldn't make it so a new issue created automatically showed up on a project board was a stopper for me.

Re: New GitHub Issues Beta

#97
post #9

I wonder how tense things are over at Atlassian right now. Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them.

For day-to-day, Jira is completely fine. I get frustrated with it when I need to dive into basic admin tasks - like spinning up a new project or board. Their admin and setting panels are completely incomprehensible. Also, Jira doesn't have a story for archiving tickets. Only a straight, permanent, hard delete with no recovery. I got reminded of this the hard way. ----- We're currently switching to Clubhouse (though a…

It's way too heavy, even for the day-to-day. A tool of that sort, for which I have to close tabs when not actively in use to save resources, even on powerful machines, or where clicking a link to a ticket might take more than very-low-hundreds of milliseconds to load, is bad.

GH issues? I click a link without thinking twice, and it's open fast. Almost every interaction is quick. I can leave a dozen tabs with GH issues open for weeks and not notice. Jira? Asana? "Ugh, a list of five issue links and I don't know which I need... fuuuuuck I don't want to open all these to find the right one, should take 10s total but will take a minute or so", and "why's my whole system feel weird? Damnit, I left Jira/Asana open again, didn't I?"

Re: New GitHub Issues Beta

#98
post #95

Earlier quoted context omitted.

Right, it turns into a political game instead of a powerful and useful tool. We have no control over how we use JIRA. It's all prescribed by someone and we don't even know who or how to reach out to them. Even the middle managers don't know how JIRA is being prescribed. They go one step worse and make Tableau dashboards from JIRA to track their own metrics that are so bad it's just... like The Office. We play the gam…

This is super common, and it's one reason why I have always volunteered (even though it sucks) to be the Jira Person. I'm experienced with it and have a good handle on how not to make it a big giant workflow mess, and I can then make sure that, by not being shy about who's running it and managing it, that feedback goes somewhere actionable.

JIRA workflow is managed by another department. Our IT department is like 50k+ employees. I think there are 100k in IT and Ops.

Re: New GitHub Issues Beta

#99
post #73

Question: how does the Table view headings reconcile to the Board view? On the Table view, there is a heading for: "Prototype", "Beta" and "Launch" https://github.githubassets.com/images/modules/site/planning... But when you look at the Board view, I don't see "Prototype", "Beta" or "Launch" denoted anywhere on the card. https://github.githubassets.com/images/modules/site/planning...

By looks of it, they're milestones :)
Post reply on HN