Auto-add issues from multiple repos or organization wide to a project table<title>

[kathy-phet]

Select Topic Area

Product Feedback

Body

Right now you can only set up an "auto-add issue" workflow for a project table to add issues from one repo. This is a significant limitation and makes the auto-add feature of limited use for our work, as we have many repos that come together for a project.

Our organization has many repos, and we would like to be able to auto-add issues from across all of our repos that meet certain search criteria on labels, or similar auto-add issues from across a subset of multiple repos.

Similar to https://github.com/orgs/community/discussions/44826, but this request also asks for organization wide auto-add capability where has no repo-specific dependency, just the search criteria.

[kylekurz]

I'd like to +1 this request, particularly in light of a 20 auto-add workflow limit on the organization. We have dozens of repositories. Even managing one project would exhaust this limit. Getting projects up for all our PMs will require an ability to have a search filter per-PM instead of per-PM*per-repo.

[DFelten]

It's possible to duplicate the workflow. Unfortunately, you can currently only do this five times.

Is there a plan to remove this limitation? We work on significantly more repositories in parallel and would therefore need this workflow more often. It would be even more practical if multiple repositories could be selected in one workflow.

[grafuzer]

+1 to this

[CarlOhlsson]

+1 to this, i have to monitor 25+ different repos for my company and this is a struggle

[rnhurt]

I really want to like GitHub Projects, but it's things like this that drive me away. It seems like it's just not a tool that can be used for real projects.

I'm not sure how GitHub uses Projects (or if they do) but I don't know how they avoided the problem of managing multiple repos in a single project. Maybe they have a special version that has these limitations removed or something. 🤷

[slagelwa]

+1

[vc1492a]

+1 we're looking to create a team roadmap project we can use to help make decisions on workflows based on a backlog of tickets cross repositories and / or other projects.

[rnhurt]

We have a "roadmap" project but it's not easy syncing it with our "daily" project. Good luck.

[lacraig2]

+1 this would be really helpful.

[lacraig2]

I saw that with https://github.com/marketplace/actions/add-to-github-projects

but it's a gross solution if I need to add that to every repo when that functionality that almost exists in Github and just needs to adjusted to be org-wide.

[kpollich]

Adding a manually-maintained GitHub action across many repos has been painful. I'd love to see this feature embraced natively so I can delete these actions and their necessary secrets, etc.

[vc1492a]

I saw that with https://github.com/marketplace/actions/add-to-github-projects

but it's a gross solution if I need to add that to every repo when that functionality that almost exists in Github and just needs to adjusted to be org-wide.

Or team wide so that Teams within an org can make decisions for their workflows

[mosk-anw]

This is a must-have requirement to be able to map multiple repos to a single project so workflows can be triggered to create respective cards/tasks when issues/bugs are created in the corresponding project, card view - Kanban board, Roadmap , bug tracker view .

[bunnybones1]

The limits of 5 and 20 for Team and Enterprise respectively are frustratingly, arbitrarily low.

BUT, I added this to about 15 repos, with one Organization-level secret, and it works fine.
https://github.com/actions/add-to-project

Not ideal but it gets the job done.

[phifuh]

1 year later and this is still a crucial missing feature