[Status: Backburner ⏳] Custom fields of a folder and being important should be attributed to tasks/issues in that folder

Hi Julien Thiery! 😊 The team continues the research here, and they have plans to work on this next year 👍 I'll let you know when I have more info.

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

My request is very similar but not exact to this one. We have an existing process where custom fields are added to task. Some tasks spawn projects while others do not. It would be helpful if the values in the custom fields on the tasks that spawn projects could be copied from the task to the project.

Thanks a lot for your detailed feedback Denise Miller! 

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

Did this end up getting worked on in 2022? Any ideas when this feature will be released? Thanks!

Hi everyone, apologies for the late reply, I was checking with our team internally to see what's the correct status here.

Our team has been researching this idea a while back, and for now, it didn't get on our Product roadmap due to significant blockers. I've changed the status here to reflect that decision. I understand it may be unwelcome news to you here. Please rest assured we will continue sharing all new feedback and vote count in this thread with our team, and if there are any changes in the future, we'll make sure to let you know. 

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

This would be a fantastic help to our team, we are spending a lot of time manually entering Custom Field values into subtasks. Our business process is that planned Projects have alignment with all Custom Fields on all subtasks. 

Hello Jess Cuddy, thank you for your comment. Would copying the values of the custom fields by dragging them in the New Table View be helpful?

l know this is not exactly what you are looking for but hopefully, it can help make your work easier. Please, let me know if you have any additional questions! 

Hi @..., yes, we already use this feature. It is helpful but we are experiencing some latency issues in Lightspeed which is making this a not so workable solution at the moment though. I've got a ticket with the support team to get this resolved so hopefully it will provide some assistance! Thanks for your help.

hi Lisa, what kind of blockers do you mean? resources, priorities?

Hey Nils Troll, it appears that those are architectural blockers. It doesn't mean our team won't do it in the future, but for now, it's not on the product roadmap. We'll keep you posted if anything changes here. 

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

Lisa Is the problem that items can be located in more than one item? If so, there must be a way to build into the architecture a method for Wrike to choose which location to inherit properties from.

Lisa are you saying that something that Workato can automate (we have done so via Workato) the engineers at Wrike cannot figure out? That's hard to believe. Why not just integrate the automation into your code?

Next to that, every custom field is already inherited from the parent, only not its value.  

Hi folks, that's all the info we have at the moment. We appreciate your inputs and we'll continue sharing all your feedback with the responsible team. If we have any updates here in the future, we'll be sure to let you know. 

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

The ability for the subtask to automatically inherit the parent task custom fields would be awesome! Also, being able to select/customize which field should and should not be inherited would be nice. For example, I want the property name to be on all the subtasks but the due dates or assignee should be different. Having to manually go in and pull down those custom fields for hundreds of tasks is a lot of manual effort. When a custom field is set up or edited a button can be selected to auto fill in all subtasks...Maybe? 

Hi Crystal Fugate, thank you for sharing your use case with us and for supporting this idea. I believe you could achieve something similar to what you're mentioning in the New Table view. In this view, you can select which fields to display and they will apply to all visible items, including subtasks. All you'd need to do is click on the "Fields" button located at the top of the view and tick the relevant field:

Once visible, you can copy the value of the parent task into the relevant subtasks by dragging the cell vertically:

I hope this option can help make your work easier. Please, let us know if you have any additional questions.

Thank you!

@... Of course dragging the value of a custom field across multiple items in table view works. It's how we make Wrike function for us now. The frustrating thing is having to do things manually that computers should be able to do automatically.

While I certainly appreciate all the automations that Wrike has been adding from time to time, however none of them are as useful as inherited values would be.

For example, if we want to automatically inform a project manager that a task in their project is complete, we should be able to see the value of the project's project manager field from the task within the project, and use that information to send them a message.

Or, if we want to see what kind of service item a task belongs to, we should be able to lookup the service item associated with the project the task is within, and then use this data to report all the time spent on that service item in the last month.

This is an important feature that is common among databases and conspicuously missing from Wrike.

I agree with Stephen Barnecut - Even there is a workaround to inherit the values to the tasks, having it as a manual process doesn't help to keep consistency and requires time and training. I have been doing the workaround @... suggests (easier since the table view was implemented), but doesn't solve the issue.

Just imagine what happens when you have a team of 50+ people working in Wrike and somebody missed to do this manual task: Your reports and dashboards are not reliable since that data depends on a manual process which as it seems, can be fully automated!

Hi Stephen Barnecut and Eduardo Cordoba, thank you for chiming in. I perfectly see why this improvement would be valuable and please rest assured that we're passing all your feedback to our Product Team 👍 I mentioned the workaround only to make sure that Crystal and other users are aware of it 🙂

Thank you for your comments and please feel free to continue sharing your feedback or any other questions you might have with us.

Just checking on this—it would be a game changer for our organization!

Hi Guy Winter, thank you for sharing your support for this suggestion, our Product Team is working on creating new options that could address this situation. Please, rest assured that we will keep you informed about any updates! 

Would love to have this as an automation option or something we can do as part of a request form

That would be a great addition to Wrike! 
Any updates on the timeline?

Hi Christoph Grüntgens, welcome to the Community! I'm afraid that we don't have additional updates about this one at the moment, however please rest assured that we will keep you informed if there are any changes 👍

Also, please allow me to suggest that you explore our New to Community forum  to uncover all the available resources within our Community 🙂

How's progress? Perhaps the devs are behind because their project managers are too busy manually propagating custom field values for them?

Adding support for this topic - the ability to inherit CDF values from the Project level is so intuitive that my team and I inherently assumed it was possible. It's disappointing to see that there's such vocal user support for this idea, and that it's not been implemented, or even given priority for development. It would be great to have public visibility to the prioritization list of new features and functionality, as the only validation we users have about this idea is the statement from forum managers that "it's been communicated to the Project Team".

Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover

Basudha Sakshyarika Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover

Bringing this back to attention as it would be a big time saver for us. When you have a plan with 300+ tasks in, the dragging functionality is time consuming and lags. Are there any plans in 2025 to bring this feature in?

Thank you!

Just upvoted! My team would find this very useful as well. We just need to have the field at the project level but have one other task within it inherit that field value. Saving the step of either setting the value in both spots or having to drag or copy/paste the value would be very helpful both from an efficiency standpoint and would also reduce the risk of the step being forgotten. 

Suggestion: a new type of Wrike Automation rule "IF [Custom Field X = empty] THEN [copy value from parent]". Would that take care of managing which custom field values get inherited?