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

GitHub Issues-only project management

blog.placemark.io

Post reply on HN
Print view View original

71–80 of 125 posts

Re: GitHub Issues-only project management

#71

Post by royandre »

zikzak wrote: post #57
simonw wrote: post #41

Earlier quoted context omitted.

Tool proliferation is definitely a problem, but at larger organizations I'm not sure how feasible it is to keep everyone using the same small set of tools. At my last large employer I ended up putting together a custom search engine that searched across a bunch of different places where important stuff ended up - Google Docs and GitHub Wikis and Markdown-in-GitHub and Confluence and Salesforce Support and a mailing l…

We used to use Unfuddle for source control and issues/PM then went to self hosted TFS but kept issues and pm in Unfuddle. Then we decided that was working so well for Dev, everyone should use it. But people didn't like Unfuddle. So now we have Asana. Everyone but Dev likes it, there's no ticket numbers, and it's confusing but at least the stakeholders are using it?

We have made a solution for assigning task numbers in Asana. Will prioritize us posting how do add it.

Re: GitHub Issues-only project management

#72

Post by ricardobeat »

polote wrote: post #63

There is no way to move an issue from repository. And this is just one example. But I guess if trello was enough, it means you don't really have bigger needs than having a list of tasks. Stop assuming the thousands of companies which use Jira are stupid

You seem offended at the thought that someone else doesn’t value the tooling you use. Why is that? There is room for different approaches.

FWIW, in my experience I haven’t seen JIRA add anything besides overhead, regardless of how tidy a PM makes it.

Re: GitHub Issues-only project management

#73

Post by bob1029 »

We've been doing this for our product for the last ~4 years. It's amazing. Getting close to 10000th issue. All the code for the whole stack lives in the repo too, so the links between code/pr/issue are flawless.

I think we still want to build another layer on top that is more about how our business works, but GH issues would continue be the one-stop-shop for anything regarding the codebase itself.

Re: GitHub Issues-only project management

#74

Post by polote »

synunlimited wrote: post #67
polote wrote: post #63

There is no way to move an issue from repository. And this is just one example. But I guess if trello was enough, it means you don't really have bigger needs than having a list of tasks. Stop assuming the thousands of companies which use Jira are stupid

Do you mean move an issue from one repository to another? Because that is totally possible now.

You are right, I totally missed that

Re: GitHub Issues-only project management

#75

Post by polote »

ricardobeat wrote: post #72
polote wrote: post #63

There is no way to move an issue from repository. And this is just one example. But I guess if trello was enough, it means you don't really have bigger needs than having a list of tasks. Stop assuming the thousands of companies which use Jira are stupid

You seem offended at the thought that someone else doesn’t value the tooling you use. Why is that? There is room for different approaches. FWIW, in my experience I haven’t seen JIRA add anything besides overhead, regardless of how tidy a PM makes it.

I hate JIRA. But if you are not a small organization, JIRA doesn't play in the same league as Github issues. Same as Notion and Confluence

Re: GitHub Issues-only project management

#76

Post by lexs »

wingmanjd wrote: post #55

We're planning a migration from Atlassian suite to the Gitlab ecosystem, but one item that I can't seem to replicate is the issue/ ticket workflow of a JIRA ticket. We have a semi-involved workflow that covers most of the software development lifecycle: initial requirements gathering, approvals, coding development, code reviews, UAT approvals, prod deployment approvals etc. How do you handle this sort of thing with j…

Scoped Labels (extended Kanban basically) and different boards for planning and development is our approach in gitlab

Re: GitHub Issues-only project management

#77

Post by Stratoscope »

I am embarrassed to admit that my most popular GitHub repo is an issues-only tracker for something I didn't even create: a popular ham and commercial handheld radio, the AnyTone AT-D868UV/AT-D878UV.

After I bought my radio, I found a few firmware issues and looked for a way to communicate them to the manufacturer. No luck on that. There was an active Facebook group, but it was a weird place run by a radio dealer who would ban you for discussing anything he thought might interfere with his business.

So I made a repo and started adding issues for the things I'd noticed. People found it and it took on a life of its own. The most popular issue is a lengthy collaboration among several hams who worked out a way to load the D878UV firmware onto later versions of the D868UV (the hardware is the same).

This was one of the topics that would get you banned on that Facebook group, as the group owner would rather sell you a new radio. The funny part is that the upgrade involves buying a special programming board and considerable time and effort, plus the risk of ruining your radio. So it was really just a labor of love for a few hams who had a blast working out how to do the upgrade.

Hams may not build our own radios as much as we used to, but we can still hack the firmware!

https://github.com/geary/AnyTone-D868UV

Re: GitHub Issues-only project management

#79

Post by civilized »

polote wrote: post #75
ricardobeat wrote: post #72

Earlier quoted context omitted.

You seem offended at the thought that someone else doesn’t value the tooling you use. Why is that? There is room for different approaches. FWIW, in my experience I haven’t seen JIRA add anything besides overhead, regardless of how tidy a PM makes it.

I hate JIRA. But if you are not a small organization, JIRA doesn't play in the same league as Github issues. Same as Notion and Confluence

I question the notion that JIRA is the only workable tool at large organizations. Many large organizations are full of small, relatively autonomous teams anyway, and those teams will benefit from a less bureaucratic tool.
Post reply on HN