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

New GitHub Issues Beta

github.com

Post reply on HN
Print view View original

211–220 of 223 posts

Re: New GitHub Issues Beta

#211

Post by arp242 »

TimWolla wrote: 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?

I kind of hate this to be honest. I understand why maintainers use them, because "i am having issues running it, plz halp", but IMHO two paragraphs of a well-written report which contains all the information is better than:

== Describe the problem (huge header) ==

Description of the the problem.

== What did you expect? ==

That it worked

== What did you get? ==

A repeat of the problem statement.

== Which version did you use? ==

Repeat of what I wrote in the description where I mentioned I tried latest release 1.2.3 and the latest master.

etc.

I generally delete these templates, making sure the requested information is all in there of course. It almost always saves significant amount of space and makes things easier to read. I haven't had any complaints thus far.

Re: New GitHub Issues Beta

#212

Post by arp242 »

mbesto wrote: post #53
tyingq wrote: 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.

> Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them. I regularly meet with tech companies in the 2~10 person dev team range and easily 70%+ still use Jira. These co's have the choice of choosing Jira (i.e. it isn't being jammed down on them by a corporate overlord) yet there's still hate? I don't get it. I'm beginning to think the Jira hate is sim…

We used Jira at a small tech company 10 years ago and I actually kind of liked it. At the time, it was the best out of a bunch of mediocre (affordable) options. It offered nice integration with our mercurial BitBucket repos and that code review tool they had (forgot the name). We just used a simple workflow, and it was overkill for what we used it for, but it worked fairly smoothly.

Haven't used it since though.

We tried to self-host initially, and our server with "only" 4G of memory (remember, this was 10 year ago, and was a respectable amount for a small office server) couldn't handle it; it was super-slow even with just a few people. lol? None of us were Java peeps and didn't really know how to tweak the JVM thing. We ended up just using the hosted option, which wasn't that expensive anyway (certainly cheaper than having a dev spend a day on this).

Re: New GitHub Issues Beta

#213

Post by chrisvalleybay »

telaandrews wrote: post #39
AdamN wrote: post #31

Earlier quoted context omitted.

Where did you end up?

We ended up using Linear and are very happy with it. Their approach is also low-level enough to be useful. Best Github integration I've seen, too.

I use Linear too and it's great. Awesome keyboard shortcuts, easy to use UX, super minimal and quite fast.

Re: New GitHub Issues Beta

#214

Post by baby »

dreamcompiler wrote: post #128
baby wrote: post #114

Earlier quoted context omitted.

Why are you using Github if not for their social features?

I can't tell if you're joking, but if not I use it because it's a reliable, free git server.

Not sure why you’d think that. Maybe this is common in your circle but I don’t know anyone who uses github just to host a remote repo.

Re: New GitHub Issues Beta

#215

Post by fergie »

rawfan wrote: post #103

There is currently a move to disable issues (in opensource projects) and the driving factor behind this, is that other people can basically put stuff on your todo-list. What would be better: - make issues read-only for non-members - track problems in discussions. often they're not really bugs and other people can directly help. If not, I'll convert the discussion to an issue when appropriate. Benefit: bugs as discuss…

I am pretty deep into open source, and have not done this myself, or seen this anywhere? Examples?

Re: New GitHub Issues Beta

#216

Post by MikusR »

tyingq wrote: 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.

They are so not bothered that they have started to "enterprise" Trello

Re: New GitHub Issues Beta

#217

Post by pyr0hu »

rawfan wrote: post #103

There is currently a move to disable issues (in opensource projects) and the driving factor behind this, is that other people can basically put stuff on your todo-list. What would be better: - make issues read-only for non-members - track problems in discussions. often they're not really bugs and other people can directly help. If not, I'll convert the discussion to an issue when appropriate. Benefit: bugs as discuss…

Yeah, but the issues page is NOT a todo-list.

Re: New GitHub Issues Beta

#218

Post by c17r »

oblio wrote: post #203
c17r wrote: post #122

Earlier quoted context omitted.

Still around, https://fogbugz.com/ but owned by somebody other than Fog Creek.

Fogbugz is Fog Creek :-)

FogBugz was renamed to Manuscript in 2017 and sold to DevFactory in 2018 who renamed it back to FogBugz.

Fog Creek renamed themselves in 2018 to Glitch after their Glitch product.

Re: New GitHub Issues Beta

#219

Post by armandososa »

fancy_pantser wrote: post #121

The UI, down to the content and styling of menus, looks a lot like Linear. I'm chuffed to see the best parts being borrowed, but it looks like they've made sub-tasks/issues too simple, as they aren't first-class issues, but mere checkboxes with short descriptions. https://linear.app

I often edit the description of an issue in linear just to breakdown the task using "markdown" checkboxes. In my mind: issues should correspond to a pull request and checkboxes to commits.

Re: New GitHub Issues Beta

#220

Post by krysp »

jmathai wrote: post #101
denimnerd42 wrote: post #51

Earlier quoted context omitted.

first step of any agile transformation is to get yourself neck deep into atlassian products. 2nd step is to setup complex JIRA workflows and reporting and use it to break all agile principles. third step is for your devs to take none of this seriously and put fake data into JIRA which your middle managers never catch onto. then your engineers who actually want to get shit done leave and you're left only with people w…

This is gold. I’m one of those engineers who left. But I didn’t leave before creating this tool for others who were staying behind. It automatically reassigns your JIRA tickets to someone else. Very handy right before stand ups and scrum of scrums where they look at who has the most open tickets. The goodbye email where I linked to this was the highlight of my career. https://github.com/jmathai/all-hands-on-deck

This is fantastic. Probably works best in a massive organisation; did that goodbye email burn any bridges?
Post reply on HN