Live data from Hacker News

GitHub Issues-only project management

blog.placemark.io

1–10 of 125 posts

Re: GitHub Issues-only project management

#6

Having to create issues-only repositories seems like a sign that one may be using the wrong tool. But the simplicity of GitHub Issues, and the fact that most issues on my plate are related to a particular repo, makes it tempting.

In a previous workplace, our security operations team (firewall) had several options for project tracking: Nothing, or Gitlab issues.

Generically, we're talking "Kanban board" with swimlanes for the status, tags for categorization, and comments/attachments for discussion tracking.

I'm currently in a position to get some people sync'ed on projects for a client, and I am going to recommend we use Trello.

Kanban is just the right level of organization and visibility without going full agile-daily-standup-sprint overload.

Re: GitHub Issues-only project management

#9
That's how we operate: Issues only. Even legal and marketing use issues.

...In their ideal form, GitHub issues are homogenous. An issue is a task that you need to complete. If it isn’t a task, it isn’t an issue. If it’s done, it’s closed. If it’s not done, it’s open.

Re: GitHub Issues-only project management

#10
post #8

Tangent, but: > or the macOS “Sticky Notes” app that somehow still exists in 2021 Why isn’t Sticky Notes just a view into a particular folder in Notes.app, anyway?

I actually still use it all the time. Just a habit from when I started using what was then OS X in '08.
Post reply on HN