Calling Enterprise customers! Try out the new auto-add workflow.

[2percentsilk]

Select Topic Area

Show & Tell

Body

We've added the ability to set up a workflow to automatically add items to your project. Check out our docs to learn more about configuring the workflow and try it out today!

[tay1orjones]

This is great! I'm glad to see this added to the workflows UI. It looks like for now this is limited to a single repo. Multi-repo support would be really beneficial for us.

We have issues from 3-4 different repos added to a single project view for triage. Right now we're doing this by having a reusable workflow .yml file across the different repos.

[john-craft]

Definitely need multi-repo support!

[cnordvik]

@tay1orjones multi-repo support is in the works! :D just hang tight :)

Any ETA on it? Just started 30-day trial to see if we can use this feature instead of Zenhub which we currently use for tracking all issues in a single board across 8 repositories 😅

[tay1orjones]

Excited to see this shipped today 🎉 Thanks!

[cnordvik]

Any chance to increase the limit from 4 to 5 or 10? We have each client in it's own repos + design so we need 5 workflows and the current limit is 4 😅

[rileybroughten]

We've increased the limit for enterprise users to 20 total auto-add workflows, check out the announcement here as well as documentation for more details 🎉

[lenzai]

Come on. Add it to the basic teams plan please!

[lfrancke]

What is disappointing about this decision is that for over a year we've been told "it's coming soon" (see my original thread from August 2021).
Never once has there been a mention of it being Enterprise only. Had there been at least we would have worked on alternatives in the meantime.

The decision is your's and it's fine for me in general, we get a lot of value for free out of Github. I'd urge you to consider announcing plans like this in advance though as that decision surely wasn't made just yesterday.

Edit: We even are on an Enterprise plan at the moment

[lenzai]

sure free plan is already feature rich.
But I don't see any reason to exclude this feature from paid plan. Excluding "teams" plan really does not make sense.

[christofferbredberg]

Would also love to see this for teams plan!

[marina-chibizova]

+1

[rileybroughten]

Auto-add workflows have been released to all users! Check out the announcement here as well as documentation for more details, as Team users can have up to 5 auto-add workflows 🎉

[heitorlessa]

I've just tested and thank you for this qualify of life improvement - I was already considering other options.

It'd be incredibly useful if this feature could:

• Set custom field values when a rule matches: e.g., is:open label:triage -> Add to the project -> set Status to Pending Review
• Ability to create multiple rules so we're not limited to adding triage issues to the board only
• Ability to work with more than one repository (nice-to-have): e.g., repository: X

[2percentsilk]

Is status the only thing you'd want to set as part of auto-add?

[debonte]

Sprint would be nice

[harvinders]

Another thing we would really appreciate, apart from extending this to multiple repositories, is an ability to move the issues to In progress when a PR is opened with linked issues.

[debonte]

Similarly, being able to move issues to Done when the associated PR is closed would be nice.

[john-craft]

Similarly, being able to move issues to Done when the associated PR is closed would be nice.

That should work indirectly already if the PR is associated with the issue. PR merge => close issue => issue marked "Done" on project.

[debonte]

Makes sense. My team doesn't close issues until the fix ships, but we move the issues to the Done column as soon as the fix is merged. Maybe we're just weird?

[ashb]

With things like Dependabot automatically opening PRs this is very annoying to deal with.

[humphreyja]

Agreed 100% with this. For our team, we have support staff that create issues labeled "bug" and would like to know if it is getting done without needing to keep reaching out to our developers on progress updates. A simple workflow called Issue Changed with a condition when PR Assigned do Set Status: In Progress would be awesome.

A step further, if there was the ability to add multiple of those, like Issue Changed when assigned to user do Set Status: Investigating.

[yngvark]

Last time i tested, I was able to use this workflow on maximum 4 repositories, this limitation is now increased or removed - great!

[d-i-bondarenko]

I've made a workflow for auto-add closed issues to project and it doesn't work.

is:issue is:closed

It shows filter but freshly closed issues don't auto-add to my "graveyard" project 😁

[rileybroughten]

@d-i-bondarenko is this issue still occurring for you?

[maiconsanson]

Hi @rileybroughten, I have a similar issue with the Auto-add to project.

When I try to add any status from an issue or pr, the filter doesn't match at all.

I've checked the generated query to filter and seems to be wrong:

-project:maiconsanson/1 is:open,closed.

Any thoughts?

[caseyokane-8451]

Any possibility of making these workflows configurable/editable via the REST API?

Also, this is probably a bit greedy but any reason why the limit is for 20 (and any chance it might be increased eventually)? Our team is trying to manage our Roadamap project (which includes 30-40 repos).

[quartercastle]

Is there any plans for increasing the limit of 20 repositories? We manage around 40-50 repositories and it would be nice if we could have them all configured to auto-add.

[oddsund]

Adding to the call for higher limit + api-configuration support.

We have more than 20 repos we want to join into one project, and while a higher limit would help to get this done, it would still be a pain to manage via clickety-clicks.

I see two options today; Github Actions Workflow or Webhook configured in settings.
For Github Action, each repository needs a Github workflow with either a PAT as a secret or a Github App secret. Neither is especially desired because of the requirement of managing the same workflow across multiple repositories, and keeping the same secret in sync across multiple repositories.

For the webhook, an external service could handle adding issues to a project, but that's more code to main, for a feature that's "almost there". Also, we have to manage a webhook across multiple repositories.

So yeah.. Higher limit + api-configuration support would be greatly appreciated 🙏

[CoderNumber1]

I'm in a similar boat to others that have commented. We would benefit greatly from increasing the auto-add workflow limit beyond 20 repositories.