Attach custom fields to child folder for sharing

Custom fields created on a top level "parent" folder are shared with the subfolders "children." However, if the subfolder is shared with someone who does not have sharing permissions on the parent folder, they cannot see those custom fields. They can manually add them back in table view, but  it would be great if there it was an option to attach those custom fields either to the parent folder or child folder so the user can decide which is most appropriate. The user should be able to answer the question: If the custom fields are applied to the subfolder, do you want these custom fields and data to be visible to users who have sharing permission on the subfolder(s) but not on the top folder where the custom fields were entered?

Upvote 8
10 comentarios
Spot On Innovative Approach Stellar Advice
Avatar

Welcome to the Community, Sofie! Thanks so much for posting your feedback here. This is an interesting idea and I see how it can be useful. A little clarification, am I right in understanding that your end goal is to be able to set Custom Fields visibility for parent and children Folders in just one place (during Custom Fields creation or editing) and have them show up in multiple locations at once?

Serge S. Community Team at Wrike Wrike Product Manager Infórmate sobre las funciones y prácticas recomendadas de Wrike

Serge S. Wrike Team member Infórmate sobre las funciones y prácticas recomendadas de Wrike

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Yes, that's correct. Currently if I create custom fields on a parent folder, they will be applied to the children folder in my view. However, if I share one of those child folders with another user who does not have sharing privileges on the parent folder, they will not see the custom fields because they don't have access to the parent folder where the custom fields live. So yes, it would result in the custom fields showing up in multiple locations at once.

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for clarifying, Sofie! We'll forward users with the similar requests here to vote for your suggestion.

Serge S. Community Team at Wrike Wrike Product Manager Infórmate sobre las funciones y prácticas recomendadas de Wrike

Serge S. Wrike Team member Infórmate sobre las funciones y prácticas recomendadas de Wrike

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi, this issue is exactly what I'm facing at the moment as well. I totally agree with Sofie.

In our case as we have > 100 projects at a time, it is not handy to ask the user(s) to add a custom field manually when we add something on top level.

I would highly appreciate if this feature would get its way into wrike.

Oliver

2
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Thank you for bumping this idea and welcome to the Community, Oliver 🙌 

Please don't forget to upvote Sofie's post, if you've not already. Thanks again for your input 👍

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hello! This is something we are looking for as well. We're moving project between folders and may not necessarily want users to see all folders within a parents folder to minimize any confusion, hence not sharing the folder with them but then the custom fields aren't showing up. 

 

Is this something that is still in the works? 

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Hi all, our Product Team are very interested in this suggestion and are discussing possible solutions internally. No information to share right now, but please keep the votes and use-cases coming!

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi. Are there any updates on this request, or is there an ETA on a solution? Our team just purchased Wrike and I'm setting up our portfolio. Having to add custom fields at the sub-project level is very burdensome, and adding a user at the custom field "paren" folder level doesn't make sense as there are users who shouldn't have that specific access.

Thanks in advance for any help you can provide.

Brigitte

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

My problem with custom fields is similar, but I would like more control over which fields are visible when the task is open for edit. The task seems to take on and show all the fields for every folder it's affiliated or tagged to. If one folder it's in has 10 custom fields, and then that task is tagged to another folder and that folder has 5 custom fields that are different the sum total of custom fields for the task is 15. There are some instances where the task will show custom fields even though its in a folder that has no custom fields active for the folder. Somehow the fields are coming from some parent folder. I even have instances where the total fields available for the task are more than the number of fields on the folder. Definitely, would like to see improvement on what fields show. I feel like if a field is shown in table view then only those fields should be shown when the task is opened for editing. 

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi everyone, thanks for adding your use-cases here, I'm passing your feedback to our Product team. For now I have no updates to share; I'll get back to you when I have news. 

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

0
Acciones de comentarios Permalink

Folllowing List for Post: Attach custom fields to child folder for sharing
[this list is visible for admins and agents only]

Arriba
Didn’t find what you were looking for? Write new post