Cascading Field Values
TL;DR
Use cascading to keep custom field values the same across parent items and subitems. When you enable cascading on a parent item, all current and new subitems inherit that value. You can change the value in a subitem at any time, then restore inheritance later to sync it with the parent again.
|
Availability: Legacy Business, Legacy Enterprise.; Unavailability: Legacy Free, Legacy Professional.; |
|
Availability: Business, Pinnacle, Apex. ; Unavailability: Free, Team; |
Cascading field values help you keep field values consistent across parent items and subitems. When you enable cascading on a field value on a parent item, subitems inherit the parent’s value. You can override that value in a subitem and restore inheritance later if you want to sync it again.
From any parent item, you can enable cascading for a custom field.
-
Once cascading is enabled:
-
All subitems show the same field value as the parent item.
-
New subitems created under that parent automatically inherit the parent’s value.
-
You can manually override the value in any subitem.
-
You can restore inheritance at any time to sync the subitem with the parent item again.
If you move an item to a new parent:
-
Cascading updates the subitem’s value to match the current value in the parent item.
-
It keeps its last value if cascading is not enabled on the new parent.
For items with more than one parent:
-
The item inherits the value from its oldest parent.
-
If that parent is removed, the item checks its remaining parents.
-
The value updates based on the next applicable parent, or stays the same if no remaining parent has cascading enabled.
Cascading works with these custom field types:
-
Single select
-
Multi-select
-
Text
-
Checkbox
-
People
-
Date
-
Link to database
Cascading also works with these system fields: Importance
Note
-
Cascaded field values can’t be rolled back to their previous value.
-
Only task-level items can have importance in Wrike.
Cascading behavior depends on how the subitem is created.
-
From a blueprint: If a parent folder or project has a cascaded custom field, that value applies to new subitems created from a blueprint inside that location. If the blueprint already includes a default value for the same custom field on the subitem, the parent’s cascaded value overrides it.
-
From a request form: If a subitem is created through a request form and the form submits a value for the same custom field, that submitted value stays as is. The parent’s cascaded value does not overwrite it. This helps preserve the responses collected through the form.
In short, cascading still keeps item creation consistent across blueprints, imports, API-created items, and request forms, but values submitted through request forms take priority over cascaded values from the parent.
Important
For items created or updated through a request form, cascading won’t overwrite:
-
Importance
-
Any custom field included in the form submission
If the form includes a field and the submitted form doesn’t contain a value for it, target folder cascading applies.
-
Open the parent item and create or select the field you want to cascade 1.
-
Enter the required value in the field 2.
-
Hover over the field, and click the cascading icon 3.
-
In the pop-up that appears, review the message, and click Apply value 4.
-
All subitems now show the same field value as the parent item.
-
To stop cascading, hover over the field again, and click X 5.
-
Open the relevant space.
-
Click Space settings 1.
-
Select the Blueprints tab 2.
-
Create a blueprint 3, or open an existing one 4.
-
Add the subprojects, tasks, or subtasks you want to include 5.
-
Create the custom fields you want to use 6.
-
Enable cascading for the relevant custom fields 7.
When you create items from the blueprint, the cascaded custom field values apply based on the parent item’s values.