[Status: Backburner ⏳] Inherited Custom Field Values

See https://help.wrike.com/hc/en-us/community/posts/115003107809-Custom-field-manager?page=1#community_comment_360002248833

Beeing able to inherit custom fields would help a lot indeed!

E.g. if I have a folder for a customer having a custom field

ABC-Status = A

I would like to inherit the content of the custom field to all folders and tasks so that e.g. in every view we can see tasks coming from an A-client.

E.g. if I have a folder for each customer with the

customer number

I would like to inherit the customer number to subfolders and tasks so that e.g. when I export something or list something I can see the customer number next to Wrike folder or taks.

This would help in many such cases.

From what I see it would be enough to define for the content of a custom field to be inherited by folders below. This custom field would not need to be changed in folders/task below so it would show the value coming from the level above but could not be changed. This should make the implementation of this feature easier than if the content of this field can be changed on each level but main thing would be to get something like this however it works...

I already suggested this 1 1/2 years ago so maybe these votes can be attributed there.

https://help.wrike.com/hc/de/community/posts/115000313265-Custom-fields-of-a-folder-and-being-important-should-be-attributed-to-tasks-issues-in-that-folder

I added my comment to the old post too as it got more votes so far.

My account managers often ask if fields can automatically populate through all of the tasks if the field is established at project level, and regardless of how many times I explain to them that Wrike does not have this set up as a feature, they continue to pester me, expressing their frustration for having to manually input this information in two different places in our templates. I understand their frustration, and so I'm writing to you, Wrike, for support with this!  Is this an issue that can be addressed, please!?!?

This would be very useful

Hi definitely need to inherit custom field values. I have projects where some custom fields only need to be filled in at the project level, not for every tasks. However, there are tasks in other projects that tag into a project that need to inherit that custom field value.

Example:

Project A has a custom date field for the First Night of a performance, but it only needs to be be input at the Project level.

Projects A-Z relate to a whole set of tasks in Project 1. So Project 1, task 1, relates to Project A; Project 1 task 2 relates to Project B; Project 1 task 3 relates to Project C; and so on).

So what I want is, for example, Project 1 task A to inherit the custom date field value for First Night from Project A when it is tagged across.

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.

https://help.wrike.com/hc/en-us/community/posts/360018897394--Status-Investigating-Cascade-Custom-Field-Value-from-Folders-Projects-to-Sub-Projects-Folders-Tasks

Recommend you all upvote this which is the same feature request: Current in investigation so it'd be good to show support if you haven't.

Thank you, George Fiveash, for sharing the thread 🙌🏼

We inject custom field values on project level when creating projects. One of those injected custom field values is the product's SAP WBS number. We need to have the SAP WBS in place in every task in the project, in order to create monthly timelog reports which include the task name, the reporter, the number of hours and the WBS number. The Finance department converts the hours to euros and adds them as internal costs to the SAP product with the WBS number as key. However, Wrike doesn't have a custom field property that would make it possible to have the field's value automatically propagated to each task in the project. We did build a custom integration that handles the inheritance of the WBS custom field also for tasks added later to the project, but we would really like to have this as a standard feature in Wrike, and thus reduce complexity in our custom-built automations. 

Hi Tuomo Suominen, thank you for sharing your use case and feedback here, I've passed it on to our team👍🏼

How's the status of this? This is one major pain point for our institution.

Hi Francisco Correia da Fonseca, thanks for reaching out, and apologies for the late reply. We are checking with the team and we'll let you know if there's an update 👍

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

Is there any update on this topic? Is the feature now available in wrike or not?

Hi Wrike TechnicalUser, thank you for bumping the thread. It's currently not available. 

Please allow me to share a little detail on how we process Product Feedback. We receive many great ideas on Community, and we pass on all feedback to our Product team. If you'd like to find out more, this article explains what happens after we receive Product feedback. 

We check with our team and assign a status after a thread receives more than 60 upvotes according to our Product Feedback Guidelines & Statuses. This suggestion at the moment needs more support. In the meantime, if there are any updates in relation to this suggestion, we'll be sure to update you here. Please let me know if you have any questions.

Adding my voice to this request. This will save an exponential number of clicks!

That feature is so important to our organization, it would be great to see it implemented in the near future.

Thank you for your continued feedback here, folks! I don't have an update at the moment, but I'll make sure to pass your feedback to 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

We absolutely need this with Lightspeed coming in, as navigating up to Projects from tasks is now not as simple as it was. So having the same CF info on the task would be extremely helpful.

Thank you very much for your feedback, Stephanie Kirk 👍

hi Lisa any news on this? When Wrike is used at larger scale this feature is essential: we need to be able to see what main project a task or risk is coming from. Using automations for this will get us over the max action in no time so that is not an option.

Hey Nils Troll and everyone! I checked with our Product team responsible for custom fields, and I was informed that they are planning to research this idea. We will let you know when we have any news to share 👍

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

Lisa This is great news!

Lisa that would be fantastic!

This would be great. What kind of timescale is realistic?

Hi David Cooper, welcome to the forums 👋

Our team is researching this idea now, and for now, it hasn't made it to planning. We'll let you know here if the team is able to add this suggestion to their roadmap. For now, please don't forget to upvote the original post above if you haven't yet because votes help the team gauge the interest here. Once it gets to 60 upvotes, we'll add one of the Product statuses here.

Please let me know if there's anything else I can help you with 🙂

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

Hi Lisa, thanks for your reply. It does make me sigh that something like this doesn't have a planned implementation despite a 5 year thread. I spend hours on workarounds using excel exports, excel formulas and pivot tables to create something that should be a simple report. 

In the original post from 2018, George Fiveash mentions a similar post by Beat Z'graggen, which now has 119 upvotes and has indeed earned a Product status. It's STATUS: BACKBURNER. Not holding my breath that this thread would earn any other status, either.

Tuomo Suominen Could you share a link to that original post?

Stephen Barnecut I was referring to the beginning of this same thread Inherited Custom Field Values (George Fiveash, July 24, 2018 09:57) which mentions Custom fields of a folder and being important should be attributed to tasks/issues in that folder (Beat Z'graggen, February 01, 2017 11:51).