We wrote a post about this recently[1]. It really depends on how you want to use them, but here are three things that might not be obvious about Projects on fi

We wrote a post about this recently[1]. It really depends on how you want to use them, but here are three things that might not be obvious about Projects on first glance: * GH Projects exist within a repo, so you can only have Issues from a single repo on a Project. * A Project contains a subset of issues within a repo - they need to be added manually to the project. This would make it tough to manage a whole project with a Project because you'd have to manually add any issue you created to it. * You can't filter issues in a Project. Fundamentally a Project is not driven by a query, it's driven by manually adding issues to a Project. So slicing and dicing issues on a Project isn't possible. I think GH Projects could be used to manage the release of an Epic (e.g. a subset of issues grouped together within a repo). But I think it'd be challenging to manage an entire project with one. 1 - http://blog.codetree.com/articles/the-important-differences-between-github-projects-and-codetree.html http://blog.codetree.com/articles/the-important-differences-...