Just gonna add myself to the list of people who think it's really important to be able to do something like this. My situation: My team is dabbling with using GH for project management. My developers all want to use Issues and PRs, because they want to be able to specify details, and they want to work at a per-repo level. My boss likes Kanban boards, both because he likes the visual layout, and because he has more things he needs to juggle so he wants less detail. The existence of organization-level Projects seemed like a two-birds-with-one-stone solution, because my boss conceptually groups multiple microservices as part of a single conceptual "chunk" of his architecture diagram (and he's right). And I don't want to have to manually synchronize with Trello every day, and I'm too lazy to go look at Atlassian products. Currently, every day I have to open every Issue and PR that might not have been added to the Project, and make sure it's in the Project. I can't even see which ones need fixing without opening them individually! This is currently a pain point that makes me wonder if I should look at some other tooling. Potential solutions: Ideally, I could automate this at a Repo level. Ideally I could specify, per-repo, one or more Projects that Issues would be auto-added to, and the same thing for PRs. Also ideally, in the list of Issues (ditto for PRs), there'd be a way to show what Projects an Issue has been assigned to. Maybe a column where if there's no Project it's blank, and if there is a Project then you can hover to see a list, or something? Heck, even just a number that counts how many Projects the Issue has been added to? And then bulk Project-assignment (for both Issues and PRs) is another option, that could be an alternative to the auto-assignment feature I described above. I imagine something like the way labels work in gmail?
... View more