GitHub issues + ZenHub is a great combo.
It works well for multirepo management. The ability to create milestones throughout multiple repos.
GitHub Issues-only project management
101–110 of 125 posts
Re: GitHub Issues-only project management
#102Earlier quoted context omitted.
Worth checking out the new GitHub Issues beta: https://github.com/features/issues/
Signed up for it to use with darklang a few weeks ago but haven't heard anything - are they adding more people to the beta?
I signed up within the first few hours of beta announcement. Still haven't got it.
I understand they want to get it "right" before opening up to the majority, but project management isn't something a business can sit and wait. People have to use some other tool in the mean time, and once having invested time and effort they won't switch back easily.
Re: GitHub Issues-only project management
#103I'd love to use this approach if only I could save issues in, you know, git. Which isn't tied to Github.
Precisely! Locking yourself to github platform and then being unable to react to whatever strange rules Microsoft applies to it, doesn't sound exciting. I suppose there could be a script that uses github API to effectively scrub all the data off a repository?
Linked elsewhere in the comments: https://github-to-sqlite.dogsheep.net/
Re: GitHub Issues-only project management
#104I wish GitHub would let you add issue only users. That is users who have access to the issues tracker but not to the code.
Can you not do this with organizations?
https://docs.github.com/en/github/creating-cloning-and-archi...
"GitHub does not provide issues-only access permissions"
Re: GitHub Issues-only project management
#105Having 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…
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.
Re: GitHub Issues-only project management
#106I'd love to use this approach if only I could save issues in, you know, git. Which isn't tied to Github.
There is this: https://github.com/dspinellis/git-issue
Re: GitHub Issues-only project management
#107I don't understand how github issues are considered for anything serious, given that they lack threading.
do you know of something similar that has threading?
I'd be the first to use something like that. Looks like I'm not the only one - https://github.com/isaacs/github/issues/837
Re: GitHub Issues-only project management
#108I was there at the time along with the OP. And, yes it did work well.
Re: GitHub Issues-only project management
#109GitHub 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,…
Can you not use an org-level project board?
Re: GitHub Issues-only project management
#110But what about the project board too?