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

Find more posts tagged with

On hold

Status: On hold

Comments

Permanently deleted user

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 👍

Devree Czupinski

I believe this alludes to having the custom fields values copy from the project level to the tasks as well as recurrence to recurrence.

Michael Michalak

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.

Evan Swanson

Here's a link to a requested feature you may be interested in:

/hc/en-us/community/posts/360018596733-Using-the-Table-View-like-an-Excel-Spreadsheet?page=1#community_comment_360002436374

Luke Hudnall

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.

Tim Schoffelman

Just for clarity - i submitted this as a feature request here: /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.

Devree Czupinski

Thank you! I just up-voted that feature!

Elizaveta Bogdanova

@Tim Thanks for submitting your feedback 👍, that section is closely monitored by our Product team.

Nancy Lawrence

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.

Elizaveta Bogdanova

@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.

Nesty Diaz

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.

Laura Boylan

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://app.workato.com/recipes/1102960?st=e5026de2b1ce6a72ba341314f298b77931ea8b97ba46cd20e3b236e5342c2736, with a fuller explanation in the Best Practices section at /hc/en-us/community/posts/360039414333.

Bethany Spaeth

Is there an update on how to build this within the native Wrike automation?

Juan Muttoni

Hi @Bethany Spaeth, thank you for your comment. I'm afraid that we don't have updates to share about this one at the moment; automation does not support this option. However, we will keep you updated if there are any changes.

Bethany Spaeth

@Laura Boylan - yes, we have a recipe set up in our Wrike Integrate; but this uses a high volume of our API calls, and I have plenty in my automation count available.

I hate paying additionally when my automations capacity has so much still available. Especially, when it is all within Wrike and I need to use Workato to sync to my other software.

Courtney Maletic

Adding a note here to agree that setting up this functionality as automation would be extremely beneficial to use our allotment of automations vs. allotment of API calls within Workato.

Rohan V

Hi @Courtney Maletic 👋 Thank you for supporting this suggestion! If you haven't already, please upvote the original post above by clicking the "thumbs up" emoji. Once the post reaches 60 upvotes, we'll be able to assign a status to it.

You can click here to learn about our Product Feedback guidelines.

Olena Pashkevych

I also need this. @Rohan V We have 62 upvotes

Basudha Sakshyarika

Welcome to the Wrike Community, @Olena Pashkevych! Thank you for checking in! 🙋🏻‍♀️

I have added the Backburner Status to this request, which means that our Product team is interested in the idea and will review it during future internal discussions. We also have a similar thread here that you can check out. Thank you! 😊

Karl Schiesz

@Basudha Sakshyarika With AI agents having been added, is cascading fields from project to tasks something that can be accomplished that way? I have been toying with various prompts with limited success, but it seems the ability to modify subtasks fields is there.