Portfolio Automations could be very useful for a number of reasons. For example, an automation could be built to add a task to multiple projects within the portfolio when a form is submitted to one of the portfolio’s projects. Or maybe a form could be submitted to a portfolio and that could create work in several different projects within the portfolio.
@PrinceUnicorn ,
Are you aware that portfolio automations were added a while ago:
Hi everyone,
Today I’m excited to announce we are introducing rules for portfolios!
With portfolio rules, you can update statuses, fields, dates, move items within portfolios, and more—all based on specific triggers you define. These are the new triggers, conditions and actions available in portfolios below:
Triggers
Conditions
Actions
Work is added to this portfolio
Status is
Move or add to a portfolio
Work is removed from this portfolio
Due date is
Get status reminder
Status is…
Also, the more recent update to the Automations builder made it more flexible to interoperate across work objects:
Hey, Community!
Rules are now Automations! with a redesigned vertical builder that shows your whole workflow from start to finish, and brings project and portfolio automations into one place.
What’s new
One automation, multiple objects
A single automation can now act across tasks, projects, and portfolios.
Task field changes → update fields, dates, status, or ownership on a project
Project changes → update its reporting portfolio
Project change meets a condition → bulk-update filter…
Does this resolve your request?
Entirely! Thank you for providing those resources! I did not know this was possible.