FREQ: Add Parent field to Entries Filter or allow displaying (but not selecting) specific Entry Types that are not selectable for an Entries field

[humandevs]

When adding Entries to an Entries field, with a lot of Entries to choose from it can be overwhelming, because Structure Entries that aren't allowed to be selected for that Entries field are hidden from the Entries selection dialog box entirely (to avoid confusion), effectively hiding the entire Structure hierarchy when selecting an Entry.

For the goal of a componentized ("Entrified") world, being able to organize and re-use Entries is key.

While I generally adhere to the "wide not deep" nesting and organization mantra, this can be a problem if you use an organizing Entry Type like 'Folder' for organizing Entries in a Structure but that organizing 'Folder' entry type shouldn't be added to the Entries field itself, and you have a lot of entries (in our case about 3000).

You can add the parent and ancestors fields to the view list of the Structure, which helps a bit, but parent is not a field that can be used to filter entries by, and adding a filter to relatedTo > [parent entry] (to limit the Entries displayed to only ones in the parent Structure) does not include the Structure children of an Entries field.

For example, we would like to restrict the "Folder" Entry Type from being able to be added to this Entries field, but if we remove it from the allowed Entry Types, it's not visible at all, and child entries are not indented, even though it exists when looking at the Entry Section elsewhere. However, Entries that have already been added to the field show up but are greyed out, indicating they can't be selected (again):

Some possible solutions:

1. A way to show specific Entry Types in the Entries Field selection but prevent those Entry Types from actually being selected (such as greying them out like as happens if you restrict multiple selections of the same entry - those entries already selected will show up in the list of Entries but be greyed out). This should be able to be limited to specific Entry Types to 'show but not allow to be selected' to limit confusion of the Entry Types used in the Structure you are selecting from.

OR

2. Adding the parent field to Entries filters so you can create an ad-hoc filter to only show entries within that 'parent' folder Structure. This is less desirable than 1) because users need to know they can create this kind of filter, rather than being able to use 1) to see and search for the folder Structure/s that are parent/s of the Entries they are looking to select.

Another option entirely would be allowing to add individual nested Entries that are owned by a matrix block or CKEditor field to an Entries field itself, allowing the parent Matrix block or CKEditor field be the 'parent' structure. Would need to be able to "move" a such nested Entry from one Matrix or CKEditor field to another without having to re-create it, though.

Some other options:

3A) Allow a card view to work like a file folder structure, where children are hidden inside a parent Structure 'Folder' entry type by default, requiring expanding the card to show the children instead of displaying them in a full list.

OR

3B) Combined with 1) allow setting a specific Structure to have children collapsed when selecting Entries by default (requiring expanding the folder 'Structure' to see and select the children you want to add).

A separate but related feature request is the ability to specify the default parent for a new Entry created from the Add Entry button of an Entries field, or even just remembering the last parent selected for that specific Entries field, so that additional Entries created and used are all (by default) organized under the same structure. Allowing Matrix block Entries to act as independent Entries that can be attached individually to an Entries field would also work for this, furthering componentization/entification while maintaining the strict organization matrix fields provide.