Add Custom Field-Based Prefixing to Tasks Launched via Automation

We’d love to see an enhancement that allows automated prefixing of tasks when launching a project from a blueprint via automation rules.

Here’s our use case:

We use an automation where, when a task in one project is marked Confirmed, it automatically launches a full project from a blueprint—complete with action items for the designated teams. These are tied to specific business locations, which we capture via a custom field.

Currently, the tasks launch without any distinguishing labels, and with this automation happening frequently across many locations, it can be difficult for users to easily understand which tasks belong to which business location without digging into the details.

We’re envisioning a feature where:

• The automation rule could assign a prefix to all tasks launched from the blueprint, using the value from a custom field (e.g., business location).

• Ideally, this could be handled by a second action in the rule builder: “Add custom field value as task prefix.”

This enhancement would significantly improve clarity, especially in team dashboards and reports where task names are the primary reference point. A pop-up to confirm the prefix might be helpful, but even a silent pull of the custom field into the task name would go a long way.

Thanks for considering—and happy to elaborate if helpful!