Agree!, at least make it so we can hide it.
I agree, this confused me so much!
An inline set should allow you to have the same set of items, but have a different name and different views depending on where you’re using it.
for example.
main task list with the views of : Today, This Week, Done
Then you create a “Dashboard” page This will have filtered views like “My Tasks”, “Work Tasks”, “Maintenance Tasks” etc…
This is just one case but there can be so many reasons to do this.
I know this has been asked before a couple of years ago, and I was hoping that with the new ios & mac os updates we would finally get it, as is such a simple thing, but sadly we got a new spaces sidebar instead.
*ᅟ I don’t know how this could be done, I would gladly do it myself if I knew how to
*ᅟThere isnt one
Oh my gosh, yes. This would be amazing. It would add SUCH a large amount of clean-up to the interfaces within columns that users can build.
I would like every inline instance of a Query or Collection to have an option for a unique title.
Currently, an inline Query or Collection is displayed with its natural title quite prominently; e.g., a Query for all Tasks is titled “Tasks”. However, within the context of the Object that includes it, this can be insufficiently informative. If filters have been applied in that instance alone to fine-tune its results to meet a need of the Object, it may not be apparent to other users or even to oneself in the future why this was done. Or if the same Query/Collection has multiple instances in the same object with different filters, distinguishing which one is which (and, again, why this was done in the first place) at a glance may be difficult.
Also, users who don’t realize that the title is universal to all instances of that Query/Collection can discover that fact the hard way after changing it in one instance while believing the change wouldn’t propagate. This happened to me at first, and to @Yif as well. I would be very surprised if it were uncommon.
When an inline Query/Collection block is created, there could be an additional text field at the top of it, or the option to add it a la the option to add a Description to an Object.
Alternatively, the existing title field itself could have an option to choose between “universal” or “this block only” (or something to that effect), with subsequent changes being applied accordingly.
As described above, this would be useful for communicating why an inline Query/Collection has been placed and/or modified within an Object. Currently, the giant titles can be both visually distracting and unhelpful, but there’s nothing the user can do about them unless the Query/Collection in question is only being used for that specific purpose.
The only workaround I’m aware of, which @kaye described in the linked thread above, is to create a new Query/Collection every time one wants a new title. However, not only can this lead to an unnecessary profusion of nearly-identical Queries/Collections, but sometimes one wants to be able to make changes to a single source that can be propagated to all of its inline instances via simple updates, as opposed to manually applying the same edit over and over. (This brings up another wish of mine, which is that such propagation could be done more automatically, but that’s a different and potentially more complicated request.)
[Edit:] Another alternative is to add a text block above the inline Query/Collection and put whatever label/info one wants in that, kind of like my first “How could it be done?” suggestion. However, this has a few issues: 1) being an additional item to keep track of, especially if the inline block gets moved, duplicated, etc., 2) additional visual clutter that could be avoided if the title itself can be changed, and 3) it doesn’t solve the unintuitiveness of the current situation, in which it’s not clear that the title is basically the only thing that when changed in one instance also changes elsewhere, per the bug-request linked above.