Explain the problem as you see it
PARENTS DESCENDANTS WITH REFS is great if you're working on the single page to have related content window open on the side and have some queries that utilise it to see a quick list of things that are in the same page.
Why is this a problem for you?
I want to work on a different page and still have the same reference to the same related content window on the side. I know I can easily just manually change that prompt to be the actual node, instead of PARENT, but I want to have it as a related content of the supertag, so that it is baked in as a template and it is set and forget, I just need to mention the node that I want as 'parent' equivalent in a field.
Suggest a solution
Please add the option to have a node mentioned in the field be the parent for the query at the 'related content' level - not individual node level/manually done. I noticed when the node is in the field because it is referenced, the "PARENTS DESCENDANTS WITH REFS" does the job but sometimes it doesn't. It's odd. potentially because it is technically nesting in somewhere else like 'today'. To have a way to set the content of a field be the 'parent' seems to be more straightforward and foolproof, as well as opening up an opportunity for more creative prompts.