List view improvements - filtering, sorting, multiple views

[marcusjroberts]

Issue description

We have the ability to create a custom list view, which is great, however, we choose list view mostly because we want to manage a large list of nodes that become unwieldy in the tree on the left.

This is a three-part feature request that I'm happy to split into different features if required.

Allow filtering

We want to be able to set a list view to filter the cards/items shown. There are multiple ways this can be done - RegEx on a field, etc, there are plenty of examples out there to draw upon for inspiration. A basic one we would use immediately, for example, is hiding all nodes where a particular value was false.

Allow nested sorting

One workaround we have done for the filtering is to sort by the value we would filter by, so that items we would prefer to be hidden, only appear at the end of the list. However, this means that the remaining nodes are no longer sorted by name, date, or whatever we chose to sort by. Having the ability to sort by X then by Y would mean that we could first push the nodes where the value was false to the bottom of the list, and then sort perhaps alphabetically by name.

Multiple list views

With the above two features implemented, we think it follows that we should be able to create multiple custom list views. We could have a view where all items are shown, for example, or another where a large number of the nodes were filtered by a particular value, etc. This would give us great utility in how we present the list of nodes to our customers.

[jmf-umbraco]

Hi Marc,

Thanks for your suggestions. I'm going to transfer this ticket over to the Umbraco CMS tracker, as the suggested functionality better belongs in the underlying CMS rather than Heartcore.

[github-actions[bot]]

Hi there @marcusjroberts!

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 🤖 🙂

[andr317c]

Hey!

Thanks for your ideas. Since these are feature requests. I will go ahead and transfer this over to discussions 😄