This one creates friction when handling tags / status in sets: When having multiple views filtered by status, you lose an object from that view if you remove the old status by hitting delete on keyboard before adding the new status. Of course the better solution is to directly choose the new status. This works fine but I mean sometime you also do it the other way. With tags it’s even more complicated since you can have multiple tags but only one status. So if you loose the object from the view you have to go back to the “All” view and put in the new value there. I think this deserves a more convenient way.
HOW TO REPRODUCE IT
Have a set with multiple conditional views
Edit tag or status by deleting the value
Dont close the prompt and put in new value
See that after clicking new option, you already lost object from that view if the condition is accordingly
I was able to provide you a video capture of the bug, here it is:
THE EXPECTED BEHAVIOR
Object should not be removed from view while editor prompt is open. After prompt is closed, conditions must be applied of course. But currently they are applied before edit prompt is closed.
Hey @sambouwer ! Realtime refresh is not really what I am missing here. Still, the other topic seems similar to this one. I think once sets get another round of polishing, those could be both addressed. But I am not sure I really understood the other report: First they talk about missing realtime refresh but then about delay to avoid instant refresh (?). I think I am missing something
Anyways, to make it clear: My problem is that sets with conditional views instantly apply changes of tags. It would indeed make sense to introduce a delay or even wait as long as the edit prompt is not closed. Especially when having multiple tags in a field, you would want to delete a few of them and then add new ones. For multi-condition views this won’t work really without switching back to the “All” view and editing there. But again, my problem is not that the views are missing realtime refresh. They are basically refreshing to quickly.
Hi @jannis, thanks for your clarification. Let’s leave them separate for now. Your point is very clear, and although I think there is at least some overlap with the other topic, they are now linked anyway. That should be enough to get the message to the devs, and that is the main point of the forum!