V14 List View / Collection configuration not fully applied.

[BenWhite27]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.1.1 / 14.2 / 14.3

Bug summary

When configuring a Collection view / List View (v13 term) on a document type we have the options for an icon, content app name, and whether to display the content app first instead of the collection. None of these properties are actually being applied when the content item for the document type is created in the content section.

Specifics

Also mentioned in the video on this issue #16858
I've seen this in my local environment I'm upgrading to v14 and also in the Umbraco.Commerce.DemoStore.

Quite annoying as in Umbraco Commerce, the product nodes have a variant collection which is always displayed first, bad experience for the content editors.

Steps to reproduce

1. Create a Document Type
2. Configure its structure and add a collection view with an icon, content app name, and the option to display the content app first.
3. In the content section, create a content node that uses that document type.
4. Observe that the collection view is always presented first, the icon is not respected, the name is not displayed.

Expected result / actual result

These configuration options should be applied as configured.

[github-actions]

Hi there @BenWhite27!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[leekelleher]

@BenWhite27 Thanks for reporting this. It has already been raised in issue #16633, so I'll close this one off.

A fix for this issue is under development, it's not quite ready yet, should be soon.
umbraco/Umbraco.CMS.Backoffice#2113