[Status: Backburner ⏳] Custom fields of a folder and being important should be attributed to tasks/issues in that folder
If I use a custom field for department (as an example) I should be able to set the department custom field of the folder to "department x" and all tasks should inherit that that are created in that folder.
If you have a folder/project for e.g. complaints or other important issues it would be great if it could be marked as important as you can do it with a task. As all new tasks in a folder would inherit the settings of its folder thus being important which helps in giving them special attention in the dahsboard etc.
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 Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with 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 Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with 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 Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with 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!
Juan Community Team at Wrike Wrike Product Manager Conosci le straordinarie funzionalità di Wrike e le best practices
Juan Wrike Team member Conosci le straordinarie funzionalità di Wrike e le best practices
Hi Juan, 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 Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with 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 Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover