Hide custom fields

Hi,

I know how to hide custom fields from list, table view and so on. But I see no possibility I can hide custom fields in the task itself.

Reason: we have some custom fields people are really using (they put numbers in, they use this numbers). But we have also custom fields which are only used by the API. So normaly no one needs to have a look into it, because the API is generating an automated report about these fields for management. These API used custom fields are making the task very confusing as their are too many tasks nobody needs in it.

So we need a possibility to hide custom fields (but they should be still available). Best would be a button in the fields area with make hidden fields visible.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Elizaveta Bogdanova

Hi @Sven Passinger, thanks a lot for posting this suggestion!

As our Product team is currently re-working the functionality that used to be called Work Templates and is getting ready to re-launch it, I think your feedback comes at a great time as more options with custom fields' visibility is on their plans 🙂

Keith Fuhrman

Hello - Could Wrike provide an update on this re-work and if it has launched? I have some members of my team asking to hide custom fields (in a task view) so that they can only see what they want.

Much Appreciated - Keith

Elizaveta Bogdanova

Hi @Keith Fuhrman, welcome to the Community 👋

Could you please let me know if you've tried using Custom item types? I'll be happy to chat and explain how they would be helpful if you'd like to customise your work items 🙂

Bernadette Cumento

Hi,

I just wanted to chime in that being able to hide custom fields (and/or sort them as suggested in this post) would be extremely beneficial for our business as well. We have multiple job types and created custom item types for each one, but that only allows us to rearrange the fields, not hide fields in tasks for jobs where they are not relevant. It also doesn't make sense for us to create a separate space just for each job type because our work would be too scattered. If it was just a matter of a few extra fields, it would be less of an issue. But one job type has over 50 custom fields and it doesn't make sense for users to be seeing this in a task that doesn't need any of them at all. Would love it if the Custom Item Types could be more customizable in this way.

Elizaveta Bogdanova

Hi @Bernadette Cumento, welcome to the forums 👋 Thanks for your contribution!

When creating/editing custom item types, it should be possible to hide custom fields using the small "eye" icon. Once hidden, they'll live in the "Hidden fields" section:

Could you please let me know if you're using this?

Bernadette Cumento

Hi Lisa,

Thank you for your reply. Yes, I use that to hide them so how I have it now is: the fields relevant to that CIT show up in the top section, i.e. the fields that show up in this accordion

but if the second section of "More fields" is expanded, i.e. the fields under this accordion

users will still see all those irrelevant fields.

In our situation we have:

Fields that need to be filled out by the person requesting the work for every task of the same CIT
Fields relevant to that CIT that need to be filled out by someone else (and not all fields would get filled out depending on the task)
Fields that exist in the account but not relevant for all CITs

What I was hoping for was to be able to use the first section for #1 and the second section for #2, instead of how we have it now which is 1# & #2 combined in the first section, and #3 in the second section.

But perhaps what would help us as well or instead would be what was suggested in this post regarding being able to group custom fields: /hc/en-us/community/posts/16140083747479-Custom-Field-Design

Juan Muttoni

Hello @Bernadette Cumento, thank you very much for your detailed reply, we understand your case better now and I've passed your feedback on to our Product Team. Please, feel free to upvote both posts 👍 We will keep you informed if any changes are applied.

If you have any other questions, please let us know.

Manisha Saini

We sometimes have a million custom fields added to the project... (ok Im exaggerating)

But if this feature is available this would help a lot.

Currently the team doesn't use custom items for personal reasons.. we got used to the task and other types. And plus we have about 70+ projects so would be harder to move or change it.

If at the project level -- at least we can figure out a way to turn off these fields that would be helpful.. then the team would decide if they want certain fields to view it from the expanded view or not...

the table view is fine.. we use it all the time but the ability to toggle on or off is a big plus!

Rohan V

Hi @Manisha Saini 👋

Thank you for sharing your detailed feedback and explaining your use case! We'll make sure your feedback is forwarded to the relevant product team. We'll keep you updated if there are any developments in the coming months.

Stephen Blanton

Also, when using custom item types, it would be nice if that custom item types fields are locked on only the fields that are specifically added and selected for the said custom item type during creation/editing.

Right now you have to add all of these custom fields that you don't want to see, to the custom item type and then hide them. Seems counter productive to have custom items types to work this way, as if someone creates or adds a new custom field for a project table, then it adds that custom field to anything under that project, even if a custom item type where you only want certain custom fields visible, then you have to go back into the custom item type editor, add these new custom fields to it, and then hide them to get it to go away.

Why not just setup custom item types so that no matter what, they only show the custom fields that were added to it during editing/creating the custom item type itself, if it wasn't added to the custom item type, then a custom field under no circumstances shows up under that custom item type out in a space. If it is needed, then someone simply needs to go and add the custom field to the custom item type to show.

Rohan V

Apologies for the delayed response, @Stephen Blanton, and thank you for your detailed feedback! 👍

There is an option to “Hide More fields section” when creating or editing a custom item type. This setting ensures that when a new custom field is added, it is not automatically included in the custom item type. However, it also hides the entire “More fields” section from view within that custom item type. I hope this might help with your use case.

That said, I’ll share your feedback with our Product Team. Thanks again for sharing your thoughts!

Sean Gilbertson

I agree with Stephen and Bernadette. A custom item type should not have any fields in it that have not been expressly added during the creation of the custom item type. We have projects in which we have around a dozen fields we want to be visible at all times. And then another dozen fields that we want to have in the "More Fields" section because they are helpful to be able to view within a project for reference when needed, but clutter up the project detail view when not needed. Having 3 separate locations for fields (Top Section that's always on, More Fields section that is collapsed by default, and Hidden Fields section which never show up in the project view, but only as a place to view unused fields during custom item creation.) Also, being able to drag fields from one location to the other when creating a custom view would also be helpful.

Rohan V

Hi @Sean Gilbertson, thank you for jumping in and sharing your detailed feedback and use case. I’ll ensure your comment is passed to the Product Team for review 👍