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.<p>Things projects have that beta projects don't:<p>* 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.<p>* No issue preview on the board.<p>Basic feature missing from sheet view:<p>* You can't sort issues along the dimensions available in a repo's issue tab (e.g. newest, oldest, recently updated).<p>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!<p>[0]: <a href="https://github.com/orgs/github/projects/4247/views/1" rel="nofollow">https://github.com/orgs/github/projects/4247/views/1</a><p>[1]: <a href="https://github.com/github/roadmap/issues/287" rel="nofollow">https://github.com/github/roadmap/issues/287</a>
I have used many different project management tools - JIRA, GitHub Projects, Trello before it belonged to Atlassian, Trello after it belonged to Atlassian, Linear, Buganizer at Google, etc. etc. etc. I have used these tools as a member of small teams (~ 5 people), a member of large teams (~ 30 people), a manager of small teams (~ 4 people), and a manager of large teams (~ 20 people).<p>I have come to the conclusion that the tool doesn't matter. The team does. The best thing to do is to keep the size of your teams small enough that people can map their work and the work adjacent to them in their heads. That is generally amazing for productivity. Expanding the scope that people have to be aware of to make progress... that's poison for productivity.<p>After I realized this, I have never spent an additional moment bitching about my project management tool. These days, I just use a Google Doc but JIRA is a prefectly good tool TBH.<p>I like GitHub projects because my team only builds open source software and we see it as a way of communicating our road map and priorities to our users and our customers. However, we have found it less ergonomic than JIRA or Google Docs. We have settled on just using GitHub issues and weekly updates in our Discord.<p>I have tried Linear and it didn't leave me impressed. Not a black mark against them, though, as this is a space where you have to be orders of magnitude better than your entrenched competition because of the inertia inherent to teams already having content on the older platforms. I can just say with confidence that they aren't an order of magnitude better than Google Docs.
We’ve been using the beta for about six months now and have really enjoyed having everything in one place. I don’t miss Jira. The GH team listens to feedback and is consistently adding new features. I would give it a try if you’re on the fence.
I am not affiliated in any way but we used GitHub projects at my last gig and transitioned to ZenHub and finally Linear and didn't look back.<p>Cannot say enough good things about Linear.
I just saw GitHub Projects for the first time as a result of this link. It looks like it has several of the key features of Asana, which is the project management tool that my very small web publishing consulting firm uses.<p>I noticed that Project Boards (<a href="https://docs.github.com/en/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards" rel="nofollow">https://docs.github.com/en/issues/organizing-your-work-with-...</a>) visually look a lot like the Board view in Asana when I'm working in a project based on the IT Project Plan template.<p>In terms of whether companies that are inclined to use web-based project management tools would drop what they are using and adopt GitHub Projects, I think the most likely candidates to do that would be companies where a great deal of the creative work already flows through GitHub and a huge percentage of the staff is in GitHub for some reason every day.<p>I don't think we would adopt this for work with clients. To the extent that our clients have GitHub as part of their toolset, the only people using it are software developers and engineers on the system administration - devops continuum. Our use of Asana is for things like project communications and high level time management, i.e. when will we hit a milestone.
Tangential but it seems like many web apps shown on HN feature a plethora of emojis. I feel like it's overused, lazy development, and therefore hurts the identity of the app when it shares the same suite of "icons" as so many other sites. At one point they were cute, but I see them absolutely everywhere now and they frankly look juvenile sometimes
This post is about GitHub but I'd like to shout out GitLab projects. It's good for my small team, we moved off Trello to that. Issues list and a simple board for visualization
The tool should be shaped around the team's best way of working.<p>The problem is that everyone thinks project/backlog organization is the silver bullet to getting things done. It's not. What they don't realize is that too much process or too little process can make or break team's autonomy.<p>I like GitHub projects. It is simple, Airtable/Notion inspired, and makes it very easy to see a backlog like a spreadsheet. The views are especially helpful for different projects, statuses, and dependencies. The best part about it? It's native to teams who work exclusively in GitHub.<p>I work on a suite of GitHub OSS repos, and this tool alone looks extremely promising. Even using the beta for a few months now has helped me put everything in one place with many views instead of having to use alternatives like ZenHub. I do everything in the open and need solutions that can be transparent with the very communities I build for.<p>This is looking good despite the bugs like editing titles in projects beta changes the issue's title on keystroke. It makes it quite easy to quickly create new issues and manage them from a single screen on the web. Big fan so far.
Neat!<p>I manage a project that spans several repos, so I've been looking for a good solution for this. I really just want something that lets me prioritize Github issues from different repos.<p>I tried Github Projects a few months ago, and I don't recall the issue, but I couldn't find any obvious way of adding issues to a project from the issue itself rather than from the project view.<p>I've been using CodeTree, which does the job, but it feels stupid paying $50/mo for a SaaS whose whole job is to just show me a list of Github issues. Especially because I haven't seen any product development at all in the year that I've been paying for it.<p>I tried Linear, and I didn't get what all the fuss was about. It's pretty, but I found it unintuitive, and it seems like it wants to be the authoritative store for bugs and tasks, when I wanted to keep them in Github and just have different views of them.<p>It looks like this latest iteration of Github Projects offers enough for me to migrate away from CodeTree and save myself the $50/month.
It is very frustrating that you can't set a default repo for issues to be created in for a project. Every single time you convert a draft to an issue you have to select a repo from a drop down of all possible repos you have available. A simple solution is just to remember the last issue repo you created and put that at the top of the list.
The problem is the future.<p>Project Mgmt should at best be where are we now, and how did we get here. You can then use that to guesstimate how long the next steps might take.<p>You can get all that out of your commit logs and tests.<p>Project Mgmt should not be about telling people what to do, but telling them they are doing the wrong thing.
Seems they've just wrapped Issues with a container having metadata. Useful yes but not until they preview Issue content in the cards themselves - useless when you have to open Issue externally to view it.
I talk to dev team leaders (EMs and PMs) multiple times a week about project management and it's quite rare that we find anyone using GitHub apart from very small teams (2-3 devs). Our research suggests product managers especially tend to prefer things like Notion/Trello and really don't like the complexity of GitHub.<p>Disclaimer: I'm a founder at Constructor (constructor.dev)
The old (non-beta) projects were quite useful as a simple kanban board integrated with Github. We used it in Firefox Graphics team with limited success. We use it actively in WebGPU group, and it works well for scoping the work for meetings.<p>I’m sure we’ve only scratched the surface of what can be done, especially with the new Projects. Excited to see how it’s going to work!
Is this the same as GitHub Projects <a href="https://github.com/features/issues" rel="nofollow">https://github.com/features/issues</a> ?
We're using the projects beta in our team of five. <a href="https://github.com/orgs/flucoma/projects/1" rel="nofollow">https://github.com/orgs/flucoma/projects/1</a> I really like the way that you can have multiple view on the same set of issues and PRS.