Standard has Config Item Relationship works the other way around
How you would think it should work (at least I did):
Make a Standard that is a bundle of other Standards, add those "Sub-Standards" to the "Main-Standard" and off we go.
We make an Request Offering and make 2 Query Results, the first on for the "Main Standard" and the Second for the related "Sub-Standards".
We relate the second Query Result to the first Query Result with a token from the first in the relationship type Standard has Config item.
And that doesn't work.
What does work is adding the "Main-Standard" to all the separate Sub-Standards.
This has something to do with the direction of the relationship, which object is Target and which is Source.
Which I think in this case is just the wrong way.
I'm going to automate this, since the relation in the Main-Standard is the primary way of doing One to Many.
But I'm really against making Many to One relationships to make this work.
Can anybody explain me why this relationship type is made the way it is and in which scenarios I could benefit from it?