Custom Fields visibility frustrations in Custom Item Types

The visibility of Custom Fields under the "More Fields" dropdown in the side panel of an item is frustrating. If I create a Custom Item Type with no fields visible in the side panel, I would expect that none show up, but that is not the case and I don't understand why?

So here I have a Custom Item type with just three fields in the top area, and nothing in the side menu

When I create a task from this item type, there is nothing in the side pain, but the More fields button is there and can be expanded to show all the fields that are in the space.

Why? This just seems messy and confusing. If I don't put the fields in the Custom Item Type, then I don't need them in that type of task. They should not be there.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Lynn Graham

I have pondered this same question and agree with Russell's suggestion.

Jonathan Beutler

Hi Russel

What I've found out so far. The custom fields listed under "More fields" are additionally driven by table views. So any custom item type that is part of that table will have that field listed under "More fields". Since it is part of that table view, it is likely that you will be able to populate that field, which will then need to be available and stored somewhere in the item type. That's probably the logic behind it.

You can get rid of this by removing the custom field from that table. (Only if the other item types don't also use it.) You can go to your space settings -> custom fields -> select the field you want to remove from a folder or project -> remove from.

Russell Sprague

Thanks @Jonathan Beutler
That makes some sense for the tables that the custom item type is in, but as you can see this table doesn't have any extra fields
It is a real inconvenience to have to go into the space custom fields and remove or add to specific folders/projects. It is my solution for now, but I really feel like the fields should follow what is set in the custom item type regardless of what is shared with the space or set in the table.

Juan Muttoni

Hi @Russell Sprague, thank you for creating this post! Our Product Team is currently exploring alternatives to optionally hide or show "More fields", we will update you as soon as we are informed of any changes 👍

Megan Brown

Hi @[Deleted User] are there any updates regarding the option to hide "more fields"? Thanks!

Arien Freymuth

Bumping this up. I'm trying to reorganize how we use automations to automatically populate custom fields.
For example:

Custom field:
Blog Type (single select)
--Skyscraper
--Long-form
--Mid-form
--Short-form
--Micro

And when a user selects the dropdown, it automatically fills in a bunch of different information across custom fields like how long we have to draft it, how long a revision should take, costs, etc.

As it stands, I can't implement a bunch of custom item types for our agency because all custom fields intended to only show for specific custom item types are populated across all other custom item types as junk/irrelevant fields. This is massively self-defeating. The fields need to either respect the user's wish to hide them entirely from the custom item type (so project managers won't see dozens of irrelevant fields), or custom fields should have the option to apply to Tasks, Projects, Folders and specific Custom Item Types.

The only workaround I have is making a generic "content" type and then using an absolutely massive, towering Single Select custom field that offers ALL variations of all of our agency's deliverables. Not ideal at all.

And it's painfully obvious that as a user I wouldn't want one custom item type's custom fields to cross-contaminate the custom fields displayed on other custom item types. I'm blown away by the fact this was overlooked. If I build a project with various custom item types in one space with unique fields for each, the "More Fields" area becomes an unnavigable scattering of custom fields. This cannot be the way. Please address this.

Iline Steyaert

Same problem here! This seems a basic...

Elizaveta Bogdanova

Hi folks! Our team has released an update some time ago - when you collapse the "More field" menu, it should remain collapsed for you for other items you open. Can you please let me know if that works like that for you?

Russell Sprague

@Elizaveta Bogdanova This works for me personally, but it is not my viewing of the extra fields that is the issue, it is other users being able to view them.

Rachel Harvey

I just spent some time investigating how our custom item types are set up to try to hide those "more fields" when I stumbled across this post. Initially, I thought this may have been a bug. I agree that I don't want others to be able to view these fields, and the collapse function doesn't quite do the trick for us.

Nana Agyekum Bannor

Is there an update on this yet.
It would really be helpful to show only populated fields and not empty ones.

Sharon Ziska

Would also like to see something more for this. In a particular space for Vendors, I have two custom item types, both task types. I have Vendor Contact and a Contract type. Obviously, the contract fields don't belong on the contact item type, but it's frustrating that I can't make them go away.

Basudha Sakshyarika

Hi everyone!

Thank you for sharing your thoughts with us. I completely see how the ability to remove the "More Fields" section could be valuable, especially for what you have mentioned. I've shared your feedback with the team. 👍🏽

Kyle Martin

I'm also in need of this function!

Rohan V

@Kyle Martin thanks for adding your support here! 🙂 Please go ahead and upvote the post above if you haven’t already done so.

Olivia Cronmiller

Having the same issue on my end. Surprised that the original post was over a year ago and no resolution to the issue. Seems like a straight forward fix.

Basudha Sakshyarika

Hi @Olivia Cronmiller. Welcome to Wrike Community! 😊🎉

Thank you for your comment. I have shared this with our product team. Our team released an update some time ago: once you collapse the "More field" menu, it should stay collapsed for all other items you open. Does that help?

Also, please make sure to upvote the original post if you haven't already. This helps our product team to determine the importance. 👍

Raimund Dienst

Hi all,

I had some trouble with this behavior as well and support team found a good, working solution for me.

Therefore you need to go to Custom Item Type, then "Add field" (even the one you do not want to see) and then actively shift this to hidden. This reduces the "more fields" menu to a barely minimum and only shows the desired custom fields in this custom item type.

Since we do have quit some custom item types and quit some custom fields, this was a good opportunity to do stupid stuff while listening to meetings... ;-)