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

Ask HN: Anyone Replace Jira with GitHub Issues?

news.ycombinator.com

Post reply on HN
Print view View original

21–26 of 26 posts

Re: Ask HN: Anyone Replace Jira with GitHub Issues?

#21

Post by ralferoo »

apologia wrote: post #14
dzhiurgis wrote: post #11

Earlier quoted context omitted.

Kinda get your sentiment, but you missed parents point. Whoever creates tickets SHOULD be able to at least skim code, do basic PR reviews, test a build. "I create tickets only" sounds like a toxic role.

Exactly. If you are capable enough to file useful tickets you are capable enough to read the code, run it locally, test out changes, tweak copy, etc. You are wasting money paying people to write tickets and not read code.

I think you have a very narrow view of software development practices. In most companies I've worked at, most tickets are created by the QA team, few of whom have ever seen the source code and there's no reason why they'd ever need to.

They raise a ticket about the problem they encounter, and then other people triage it and try to find a way to reliably repro the issue, and then it gets passed to the development team when there's something actionable.

Re: Ask HN: Anyone Replace Jira with GitHub Issues?

#22

Post by samieljabali »

dzhiurgis wrote: post #12

What's your plan with documentation - wiki or markdown files in source? Google seems to document everything in repo - which is brilliant since it can be reviewed, you can ask PR author to update doc and hence less likely to go out of sync.

> wiki or markdown files in source

Exactly.

Re: Ask HN: Anyone Replace Jira with GitHub Issues?

#23

Post by samieljabali »

bobx11 wrote: post #5

I have ticket only repos where people can create tickets. They get pulled into a project and mentions across repos are still shown with status. We create issues from a user form too! It’s nice to get away from using multiple systems and get conversations so close to the pull requests.

> I have ticket only repos where people can create tickets.

Nice thinking.

> We create issues from a user form too!

This is where the money's at. I'm assuming this was done via Github API + Generated Token. I was thinking of something similar to this, however using a Slackbot.

Re: Ask HN: Anyone Replace Jira with GitHub Issues?

#24

Post by dzhiurgis »

ralferoo wrote: post #21
apologia wrote: post #14

Earlier quoted context omitted.

Exactly. If you are capable enough to file useful tickets you are capable enough to read the code, run it locally, test out changes, tweak copy, etc. You are wasting money paying people to write tickets and not read code.

I think you have a very narrow view of software development practices. In most companies I've worked at, most tickets are created by the QA team, few of whom have ever seen the source code and there's no reason why they'd ever need to. They raise a ticket about the problem they encounter, and then other people triage it and try to find a way to reliably repro the issue, and then it gets passed to the development team…

I've worked in various companies as a developer and my worst experiences were where access to code is restricted, but BA's create these esoteric tickets with about 3 words in description...

I'm happy for them to raise tickets within their realm (and by the way lets not conflate support tickets vs actual work items), but please have some manager sift them thru into something meaningful.

Re: Ask HN: Anyone Replace Jira with GitHub Issues?

#25

Post by dzhiurgis »

atonse wrote: post #13
dzhiurgis wrote: post #11

Earlier quoted context omitted.

Kinda get your sentiment, but you missed parents point. Whoever creates tickets SHOULD be able to at least skim code, do basic PR reviews, test a build. "I create tickets only" sounds like a toxic role.

What’s toxic about it? Tickets have a business need. They may have notes on implementation but if they aren’t serving a business need why do they exist?

IMO business needs shouldn't be a ticket - have some refinement first then explain clearly what do you want me to do.

IDK why it's hard for me to explain my sentiment, but I've worked in corp environments with large teams of averages using JIRA vs small teams of smart remote people. In the later my tickets were almost always very clear resulting in 1 or 2 short and tactical meetings per week. In corp environment I have 10 meetings per week spanning hours. The productivity is easily 10x worse.

Re: Ask HN: Anyone Replace Jira with GitHub Issues?

#26

Post by dev_0 »

genmud wrote: post #15
ozim wrote: post #9

Earlier quoted context omitted.

I might be security LARPing but if someone doesn’t need to read the code to be able to do his job he just shouldn’t have access to do it. Person might have been trustworthy when they were hired and they might change their mind at some point. Even better - they still might be trustworthy but their computer got compromised and someone might be using them. Maybe some other employee has problems with them and since they…

I’m an actual security guy, been doing it for nearly 20 years (before it was a thing). I’m of the opinion that if I can’t trust people to look at code, they shouldn’t be at the company. Period. There are very few use cases where I believe read only access to code from people in product, engineering or support should be restricted. Generally the net benefit is well worth the potential risk introduced. If you are worri…

[dead]
Post reply on HN