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

111–120 of 125 posts

Re: GitHub Issues-only project management

#111

Post by toastal »

gregd wrote: post #38

GitHub issues is great, until and unless you work for a company that doesn't allow 3rd party access to the Org where all your repos live. I want and need a one-stop shop for my Kanban board and I could accomplish this using GitKraken Boards for instance, but because of where I work, they disallow GitKraken access to my repo issues. So now, managing a dozen or more repos with an issue tracker for each one separately,…

That sounds like a good thing to not let a mega-corp access to your private repos or require users to check another terms of service to another yet another service to get access to Issues.

Re: GitHub Issues-only project management

#112

Post by lugged »

bastardoperator wrote: post #105
madeofpalk wrote: post #87

Earlier quoted context omitted.

The open source company im at uses Github Issues/Projects exclusively for project management, and I'm not a fan, though I do think it's the least worst option - using any other system would require a really weird and bad way to sync the issues that are reported publicly. Github just lacks the few necessary to do project management well, I think. I would love a "backlog view" for Github Projects.

You could just create a column and or use label called backlog.

Colin sorting or splitting would be amazing for GitHub. The convert to issue feature needs work though.

Re: GitHub Issues-only project management

#114

Post by jimmySixDOF »

TeMPOraL wrote: post #37

Nope. Having worked in a shop that used GitLab issues for project management, I've come to realize GitHub-style issue trackers work if all your project management boils down to creating and tracking bite-sized blobs of work. It stops being sufficient when you need to actually plan ahead . FWIW, so does Trello. Couple reasons why: - Issues are flat. Work breaks down into a tree. And no, "epic / ticket / checkboxes in…

I have worked in large job environments with Primivera or MS Project maintained by dedicated resources. The overhead they add make sense for a wide view of multiple department swimlanes across a complete effort life cycle. My experience here is your WBS should keep the activity line items way above the level of anything in a Github issue. A L5 WBS plan might go [PROJECT_A > PHASE_2 > DATA CENTER > COMMON_SVC > SINGLE SIGNON {5d Duration | 3 Engineers x 10 Hours}] -- SSO itself might be a 30 point todo list for 5 people but those will be managed separately closer to the ground as the work approaches and runs through using a sharper tool - and if the team is ok with GitHub issues then fine there are a hundred ways to do it and none of them perfect; but it would get messy fast using a full blown PMO Software package for backlog type issues. If you had to add another level to WBS it would be generic milestone activity like Prototype/Test/Deploy dates.

Re: GitHub Issues-only project management

#115

Post by derefr »

handrous wrote: post #83
derefr wrote: 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?

Notes.app can hold so much more than would work in a sticky. Whole embedded PDFs in the middle of a note, images, tables.

Sticky Notes are full RTF documents, and can at least hold embedded images. (Not sure about the other things, I haven't tried.)

Re: GitHub Issues-only project management

#116

Post by cjaybo »

lugged wrote: post #113
patrickdavey wrote: post #98

I wish GitHub would let you add issue only users. That is users who have access to the issues tracker but not to the code.

This thread is about issue only GitHub repos being used for project management.

Is there some reason you think the GP missed this point? Being able to restrict user access to issues-only would make using GH for project management a bit "cleaner", regardless of whether the repo is issue only or not.

Re: GitHub Issues-only project management

#117

Post by skinnymuch »

aetherspawn wrote: post #94

`Microsoft To Do` works great as an issues-only repository that syncs well between multiple users and devices, integrates with Outlook (flagging an email automatically imports an issue) and has i.e. excellent native desktop and mobile apps. Once I started using Microsoft To Do, the way that I ran my life/business scheduling became 10-fold more efficient. Any recurring tasks or issues, be it daily, weekly, annually, c…

Isn’t Microsoft To Do built off and based in on their acquisition of Wunderlist? So Wunderlist essentially/mostly made it.

I believe a lot of vocal fans of Wunderlist were upset with how it all went down and didn’t want Microsoft To Do. So there’s lots of internet vocal negativity toward the app possibly.

Re: GitHub Issues-only project management

#118

Post by rkda »

antipaul wrote: post #59

I wish. I’m at Big Corp where key project collaborators and stakeholders are wildly non technical and there’s no way to use GitHub issues. They mostly use only email. What is a more accessible alternative? I’ve been trying google docs. Thoughts?

What about Discourse? You can configure it so they only interact with it via email.

https://meta.discourse.org/t/running-a-project-or-team-using...

Re: GitHub Issues-only project management

#119

Post by quesodev »

mwcampbell wrote: post #33
quesodev wrote: post #23

Having run several engineering teams (15-20 people), I used this approach extensively. It meant one less place to go and one less tool to use. I liked this approach so much, I also wanted to use Github Issues for internal and external customer support instead of having another help desk tool involved. I created https://hubdesk.io/ as a side project to do this. Forward your support emails to HubDesk and it creates a G…

HubDesk looks nice. A couple of questions though: 1. Would I have control over the "From" name and address for emails that HubDesk sends to users? 2. Do email replies from users get added as comments on the issue? 3. When an issue is created, does HubDesk send a confirmation to the user so they can do follow-up replies even before the rep has done an outward-facing reply?

For #1, Currently the response uses your custom email address as the Reply-To address, but the email comes from a hubdesk.io email address. It's on my list to add support for custom domains.

For #2, yes. You can go back a forth with the user just using commments.

For #3, that's also on my list to add.

Thanks for the feedback!

Re: GitHub Issues-only project management

#120

Post by quesodev »

codesternews wrote: post #47
quesodev wrote: post #23

Having run several engineering teams (15-20 people), I used this approach extensively. It meant one less place to go and one less tool to use. I liked this approach so much, I also wanted to use Github Issues for internal and external customer support instead of having another help desk tool involved. I created https://hubdesk.io/ as a side project to do this. Forward your support emails to HubDesk and it creates a G…

Not related but your landing page is good. May I know what template/how did you build it. Thanks

Yes, it's https://tailwindui.com/.
Post reply on HN