Limitations in Workfront Planning Automations Feature

Preserve Connected Record Picklist Values in Automations

In Workfront Planning, I’d love the ability to create a record and send it to another record type, either within the same workspace or across workspaces, while preserving picklist values from connected records.

Right now, when using automations, those picklist values don’t carry over if they come from connected records. For teams using a central taxonomy model, this becomes a real challenge. We end up having to rely on Fusion to handle what feels like a core in-app use case, including working through complex JSON structures and API calls just to pass multi-select values. It works, but it adds a lot of unnecessary complexity for something that should be native.

Automatically Associate Projects to Portfolios and Programs

There’s also a related gap when creating portfolios and programs through automations. While you can create them, there’s no way to automatically associate the projects generated from those automations back to the portfolio or program.

That again forces a dependency on Fusion where it would be much more intuitive and efficient to manage this directly in Planning.

Why This Matters

Bringing these capabilities fully into the in-app automation experience would simplify architecture, reduce reliance on Fusion for common use cases, and make Planning much more scalable for organizations managing centralized taxonomies and structured hierarchies.