Cascade Custom Fields from Project to Tasks
It would be a great benefit to be able to cascade custom fields at the project level down to individual tasks in the project. Reading other forum comments this will also help with reporting, which I agree with. It makes the report more digestible, specifically when shared with leadership who may not be users in Wrike.
help.wrike.com/hc/en-us/articles/360005778794-New-Table-View
Hi Luke, welcome to back to the Community! Sorry in advance if I misunderstood your suggestion here.
By cascade, do you mean include Project's Custom Fields at the Task level? This is possible, you select where to apply Custom Fields when creating them. Check out this article and let me know if this helps 👍
I believe this alludes to having the custom fields values copy from the project level to the tasks as well as recurrence to recurrence.
Luke,
Our business uses this extensively. We have our tech partners build custom API's to do cascade customer information for example (name, unique identifier ect.) from the project level down to each task and sub-task.
Here's a link to a requested feature you may be interested in:
https://help.wrike.com/hc/en-us/community/posts/360018596733-Using-the-Table-View-like-an-Excel-Spreadsheet?page=1#community_comment_360002436374
Michael,
Interesting to hear. It would be great if the feature were available in Wrike. I am not sure an API is the right solution for our organization but thank you for the suggestion.
Just for clarity - i submitted this as a feature request here: https://help.wrike.com/hc/en-us/community/posts/360018897394-Cascade-Custom-Field-Value-from-Folders-Projects-to-Sub-Projects-Folders-Tasks
@Michael Michalak - do you know how many updates to the API that would be on a daily basis? Seems to me that if Wrike built something internally, they could cut down on the API calls people are doing in order to make up for this feature not being in place.
Thank you! I just up-voted that feature!
@Tim Thanks for submitting your feedback 👍, that section is closely monitored by our Product team.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
I totally agree with the above. It is extra and redundant work to populate custom fields at the project level only to have to populate those same custom fields at the task level. We rely on custom field a lot for our reports and I'm disappointed that in order to have accurate and reliable reporting, we have to do extra manual work. It's a time-waster and also opens the door for mistakes. I'll up vote this as well. Thanks.
@Nancy Hey, thanks for adding your use-case here and an upvote for the feature in the Product Feedback section 👍 I can see that it's a very popular feature request - it's only added a month ago and already has 31 votes. It will surely be brought to our Product team's attention soon.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
I completely agree with this! We use a request form to populate metadata into project custom fields, but then have to update tasks manually. It's extremely inefficient. Hopefully we can get an enhancement soon! I've up-voted in the product feedback section as well.
If you have access to Wrike Integrate (paid add-on), it's possible to automatically copy the value from a project-level custom field (i.e., Client) to all new tasks created within that project.
I posted an example community recipe at https://www.workato.com/recipes/1102960, with a fuller explanation in the Best Practices section at https://help.wrike.com/hc/en-us/community/posts/360039414333.