I also found myself closing them. Much better now.
Indeed. I often find myself starring at duplicates:
@chrisCV also mentions this. Knowing the ancestors (or at least the parent) would help.
Most of my tasks that I link to from an agenda are more like projects that contain subtasks. I never wanted to close what I link to from inside an item. This new closing behavior is very distracting for me. Closing used to be a very elementary action, and I wouldn’t want a behavior depending on the content (i. e., whether there is a link inside) with a popup + navigation + confirmation for an elementary action.
And it’s confusing what ESC does. And closing/opening behaves differently if the target is a list (actually, that’s the behavior that I want).
It also conflicts with my mental model. A link is not the target. Whatever I do with an item should not harm the target of a link that happens to be inside the description of an item. It breaks a boundary. Closing/opening changed to a context-sensitive, boundary-breaking action.
For me, more useful would be the ability to close an item from the backlinks when cleaning up. But it’s a very minor thing; and the action would be made on a backlink, not on an item.
The visual distinction between a “closed item with a link to a closed item” and an “open item with a link to a closed item” could be more distinctive. (The meaning of the latter may appear strange. But happens: E. g., a leftover from the last agenda that was not discussed; and in the meantime, someone completed the task. It still was not discussed.)
Originall, I wanted to add some issues of my own in this post, but commenting on the above took more than expected.