nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Are there any plans to allow Pinned fields to be customizable by View

daniel_jones_58rpy9

I have many pinned custom fields, and for the vast majority of views, they work well. However, there are some views, now that Idea Types have been introduced, where those custom fields are irrelevant. It would be great if I could hide custom fields by Idea Type or by View. Thoughts?

Accepted answers

Tanguy Crusson

We've started working on this: it's not about hiding fields but letting you configure pinned fields for each type. Would that work? You can always collapse the "other fields" section (and it should stay collapsed).

image (50).png

All comments

Tanguy Crusson

image (50).png

Lissa Radman_r40qf0

@Tanguy CrussonThis is a helpful first step. We’re finding that unique fields by type are needed. While collapsing provides a short-term workaround, it still creates a somewhat messy experience and raises questions for others in the organization who review JPD, as well as for new members joining Product.

In the ideal state, I would want to be able to determine what fields can be displayed (pinned or other fields) per Type

Andre Martins_3pdc1c

Hi, do you have an estimate about it?

Tanguy Crusson

Still a few weeks out. We don't usually give estimates (because most times they are wrong) and in this case I'm glad we didn't: we had a perfectly working solution and realised it introduced a whole bunch of performance regressions. We're on it