I've been amazed at how effective pullreminders is at helping our teams stay focused on finishing work we've started. In fact, pullpanda seems more effective in this regard than many of the various task/kanban products I've tried.
Today, this awesomeness is concentrated around pull requests. That covers a lot of ground, but our team has plenty of work that does not begin or end with a pull request. Perhaps with the help of GitHub Projects, it might be possible to close this gap using issues. Issues are a little more challenging because they often have an (implied) order in priority/value in addition to the obvious ordering from oldest/stalest. And only within Projects can issues have the natural open-draft-reviewed-(merged|closed) flow that PRs have.
But squinting slightly, the key reminders, analytics, and assignment features of pullpanda translate nicely to the issues case. Certainly, integration with issues would be very valuable for the teams I've worked with and would make GitHub super sticky.
I've been amazed at how effective pullreminders is at helping our teams stay focused on finishing work we've started. In fact, pullpanda seems more effective in this regard than many of the various task/kanban products I've tried.
Today, this awesomeness is concentrated around pull requests. That covers a lot of ground, but our team has plenty of work that does not begin or end with a pull request. Perhaps with the help of GitHub Projects, it might be possible to close this gap using issues. Issues are a little more challenging because they often have an (implied) order in priority/value in addition to the obvious ordering from oldest/stalest. And only within Projects can issues have the natural open-draft-reviewed-(merged|closed) flow that PRs have.
But squinting slightly, the key reminders, analytics, and assignment features of pullpanda translate nicely to the issues case. Certainly, integration with issues would be very valuable for the teams I've worked with and would make GitHub super sticky.
<3!