Live data from Hacker News

New GitHub Issues Beta

github.com

21–30 of 223 posts

Re: New GitHub Issues Beta

#21
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.

Probably not that tense. A lot of enterprises with Very Big Licenses are hard-locked into Atlassian products with little to no chance of changing.

The problem is once you connect Jira to Confluence to Team Calendars to Crowd to BitBucket Server you're very deep into the lock-in.

Nobody has either the time or the will to switch because, while all the software kind of sucks, it doesn't suck enough to the point where someone is going to stop working on their product and/or service to jettison Atlassian from their org.

Re: New GitHub Issues Beta

#22
post #5

I'm more interested in GitHub's Issue Forms (as an evolution of Issue Templates): https://twitter.com/frenck/status/1355620350176976901 Does anyone know what the status of these is?

> Dive into work faster with issue forms and templates

Looks like its the same alpha/beta.

Re: New GitHub Issues Beta

#23
I am longing for the day they deprecate Azure Devops and merge it into GitHub Enterprise.

This is the only way I’ll ever get the ability to work with GitHub in my company, which has a much superior UI/UX imo.

Re: New GitHub Issues Beta

#24
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.

[deleted]

Re: New GitHub Issues Beta

#25
I can't tell if they've handled it here, but one of the things I'd love to see is a "friendly" view into issues for non-coders. In my experience, when a non-coder sees something that "looks like code" they become confused and frightened and generally avoid the interface.

Re: New GitHub Issues Beta

#26
It floors me that they haven't addressed the underlying architecture issues that made Issues unusable: Issues are only for a single repo. Business users don't (and shouldn't) know what repo to add an Issue to. This is why we moved away from Issues and none of these new visualizations make the product usable until they deliver multi-repo issues.

Re: New GitHub Issues Beta

#27
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 dont see this new feature as a threat to Jira. For some tech-focused companies, sure it might make sense that everyone is in Github as their overarching project management. For all the other "regular" businesses, Jira is a more 'party neutral' solution.

Re: New GitHub Issues Beta

#28
post #5

I'm more interested in GitHub's Issue Forms (as an evolution of Issue Templates): https://twitter.com/frenck/status/1355620350176976901 Does anyone know what the status of these is?

> Dive into work faster with issue forms and templates Looks like its the same alpha/beta.

Thanks. I missed that list item, because it did not have a corresponding screenshot / screencast.

Re: New GitHub Issues Beta

#29
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?

Re: New GitHub Issues Beta

#30
"it's just a spreadsheet, and [view X] is a filter on that sheet" is a nice mental model. I've had lots of managers organize stuff in google sheets and then copy to [task manager X] simply because it's easier to think about - they'd probably love this. I certainly would, vs Jira's massive "everything is custom UI / a unique concept" mess.
Post reply on HN