4 ms·

I've been working on using github projects beta for the past couple months. I'm super excited for it, but right now it's hard to use because because it lacks b

by closed 5y ago

I've been working on using github projects beta for the past couple months. I'm super excited for it, but right now it's hard to use because because it lacks basic features. Things projects have that beta projects don't: * No easy way to automatically add issues from a repo to your project. You have to add them one by one, or use the graphql API, which lacks batch operations. * No issue preview on the board. Basic feature missing from sheet view: * You can't sort issues along the dimensions available in a repo's issue tab (e.g. newest, oldest, recently updated). I thought I must have been missing something, until I realized that github's public roadmap repo itself uses a bot to add issues [0]. There's an issue there listing out the parity items [1], which will be super handy! [0]: https://github.com/orgs/github/projects/4247/views/1 https://github.com/orgs/github/projects/4247/views/1 [1]: https://github.com/github/roadmap/issues/287 https://github.com/github/roadmap/issues/287

joegahona 5y ago
Our team is really struggling with Projects for these and many other reasons. The most annoying thing is they hijack CMD+F to use their command-line-like filter, which prevents me from quickly finding words that I want to see on the page. There's also no way to just simply make a ticket from the board itself, and the main value prop of using a Github product -- keeping Engineers in the Github environment without having to have multiple tabs opened -- is completely wiped out by Projects opening a new tab for anything you click on. Not impressed so far.
dralley 5y ago
> * No easy way to automatically add issues from a repo to your project. You have to add them one by one, or use the graphql API, which lacks batch operations. Yup. I spent an hour evaluating it last weekend, and this is where I stopped. It's difficult to make good use out of so many of the features when there's no way to bulk-add issues to the project tracker.
- drcongo 5y ago
  I got really excited for this when they previewed it a while back but the thing we got just feels like a hobbled spreadsheet with a lot of usability issues.

by closed 5y ago

joegahona 5y ago

Our team is really struggling with Projects for these and many other reasons. The most annoying thing is they hijack CMD+F to use their command-line-like filter, which prevents me from quickly finding words that I want to see on the page. There's also no way to just simply make a ticket from the board itself, and the main value prop of using a Github product -- keeping Engineers in the Github environment without having to have multiple tabs opened -- is completely wiped out by Projects opening a new tab for anything you click on. Not impressed so far.

dralley 5y ago

> * No easy way to automatically add issues from a repo to your project. You have to add them one by one, or use the graphql API, which lacks batch operations. Yup. I spent an hour evaluating it last weekend, and this is where I stopped. It's difficult to make good use out of so many of the features when there's no way to bulk-add issues to the project tracker.

drcongo 5y ago
I got really excited for this when they previewed it a while back but the thing we got just feels like a hobbled spreadsheet with a lot of usability issues.