[Status: Backburner ⏳] Custom Fields | Hide or Show on Project Level

Hi everyone, apologies for the delay in sharing an update here. I've checked with our team and currently, there are no updates in relation to this suggestion. We'll be sure to update you here if there are any changes 🙋🏻‍♀️

I was tasked with removing custom fields from projects or tasks only to find that it is not possible to remove from projects.  This led me to this thread.  This request is nearly 5 years old with little information on when/if this feature will be added.  I'd like to know if this is on any roadmap for future releases or has been determined to be too difficult to implement?

Hi Michael Kuhlmann, welcome to the Community and thank you for taking the time to share your feedback. Please allow me to share a bit more on how our Product Feedback forum works. We have a voting system, and once any suggestion gets reaches 60 upvotes from the Community, it receives a product status from the team. You can find out more about our Guidelines and Statuses here. For this reason, please make sure to upvote the original post above if you haven't yet - the number of votes helps the team understand how popular the suggestion is.

In the meanwhile, if there are any changes in relation to this suggestion, we'll be sure to update you here. 

I want to hide a few custom fields in listview for certain folders in my space.  Is there a way to do this?  Or, is this the feature request listed in this thread that hasn't been done by Wrike?

Hi Krista Beem, you can create a Space level custom field and restrict it to only certain folders so it won't show on each folder. 

Thanks, Cansu.  When I try to designate custom fields at the space level, I get a prompt to "Convert to account field."  Do I need to convert to an account field before I can set access to fields at the folder level?  Also, when I try to remove fields from certain folders, the folder is not always available in the popup.

I think this Wrike Webpage needs to be updated to include an additional section:  Hide a custom field from the List View.

Hi Krista Beem, I see that you're in touch with our Support team in relation to this, can I help you with anything else? 

Is the ability to apply custom fields to tasks only still on the roadmap? I'm seeing this request originated in 2017 with no progress.

Hi Eric Sayasene and everyone! This has recently become possible with Custom Item Types - you can create a project-based item and hyde custom fields on the panel. Does it help in your case? 

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 doesn't really fix the issue. We were trying to implement custom item types but there are still too many bugs and limitations, especially with the ability to upload tasks. Unless there are plans to merge regular tasks with custom item types, we still need the ability to make custom fields only show up in tasks.

Got you, thanks a lot for clarifying Eric Sayasene, I'll be passing your feedback to the 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

Yes, this would be most helpful to show custom fields in various areas: dashboard, board view, project level, etc.  We use a custom field for customer name, project number, etc.

Thank you for supporting this suggestion Aaron Gerlach🙌🏼

This question doesn't seem to have been answered yet...I have project CITs and task CITs created in my space. When I create new projects and tasks from these via form, the custom fields that I've hidden and shown aren't preserved; everything shows again! We're trying desperately to find a way to show/hide custom fields based on project vs task, but it just doesn't seem possible yet. 

Hi folks! As this idea reached 60 upvotes, I've asked the respective Product team to provide a status here. They find this idea useful, but they don't have any concrete plans for this at the moment. I've added a status to reflect that outlook. We'll continue sharing your feedback with the 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

After finding multiple threads on this same issue, it looks like this might be the "official" thread. This issue is so incredibly frustrating. We spent months rebuilding entire structures for our project management. I was doing final testing and could not figure out why these strange fields were showing up at a Project Level. They are custom fields associated with a custom item type located within folders deep within the project but they are rolling up to the Project Level.....makes no sense!

Hi Todd Kelvington, thank you for sharing your use case with us. I understand this would be an important feature for you and your team and I've passed your comments on to our Product Development team. Please, let us know if there is anything else we could help with.

Would like to chime in here as well. 

As we are trying to organize projects, there is just no need for task level custom fields to appear on my project. It clutters the project and makes finding the useful fields at the project level difficult if you have many customer fields. 

Creating a custom item type is great but not being able to choose which custom fields should be in use on those custom items types and having to accept that all custom fields in a space will appear on all tasks is terribly frustrating. Not all tasks relate and thus do not need all of the same custom fields. Projects also dont need those fields. 

Hi Daniel Glowack, thank you for sharing your feedback with us, we'll send it to our team now. 

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

Hey!

Any positive updates about this popular request? Our team faces the same situation with the custom fields in the project info panels. We need to hide the custom fields in the project info panel without reorganizing our folders structure.

Thanks!

Hi Marie-Pier Couture, no updates at the moment. 

Thanks for sharing your feedback, it's now passed on to our 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

Hi there,

I am also in desperate need of this feature. I'm currently creating support tickets, and I've encountered an issue where all my custom field types for the individual ticket are visible on higher-level projects and folders. It's incredibly frustrating not being able to hide these fields on other levels and only have them displayed at the task-level.

Thank you for sharing your feedback Tim Hansen, we appreciate it. 

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 have several years of comments and requests around this issue. I am not sure why Custom Fields you apply to a Project, Task, Folder, or Custom Item type continue to show up in unrelated items. Every time we create a custom item type and use custom fields, we have to go back through our entire Project Management structure and try to "trick" the system.

Custom Item Type 1 created with Custom Fields A, B, and C........Custom Item Type 2 Created with Custom Fields D, E, and F.  Open up the project and Custom Item Type 2 now has custom fields A, B, C, D, E, and F.  Over the course of type, elements are taking on dozens of custom fields that are totally unrelated to item being managed. How is this acceptable?

Go into the settings for Custom Item Type 2 - Custom fields A, B, C are not showing up in the settings so why are they appearing in an actual project item? Wrike hack - add A, B, C custom field and then immediately hide them. Works for a bit, until somebody creates a new custom field and then the scavenger hunt starts all over again to find out where that new field is showing up.

What additional information does Wrike need to prioritize this fix????

Thanks for sharing your thoughts, Todd Kelvington! 😊

I totally understand how important this suggestion is. Our team carefully reviews all input to see what's feasible and prioritizes accordingly. While we don't have an update right now for this particular suggestion, I'll be sure to keep you in the loop if there's any news in the coming months, as our product team evaluates suggestions and plans for next year. 👍🏽

Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover

I keep going to threads and up voting items that have been "in the works" for several years.  There is several years of comments from the Wrike Team saying "thanks, we hear you and I will pass this along to our product development team" Is there a point when you could consider taking some of these back burner items and putting them in a customer survey to see what the customers want? Some of this appears to be low hanging fruit that could benefit a large group of customers.  Our two biggest frustrations are this item and the inability to have field data flow from Project to Task level within a project. I realize that the field data flow request is not low hanging fruit but seems task level only custom fields should be.