Application of Routes isn't transitive

With a setup like this:

• Proxy Repo "Atlassian"
• Group "Public" which contains X
• Group "FID" which contains Public

We set up an Inclusive route (with value ./.*atlassian./.*), put just "Atlassian" in the Ordered Route Repos list, and then Repository Group as "All Repository Groups". However this meant nobody was able to pull down Atlassian artifacts. By turning logging up to debug and picking through the output we saw the routing logic was saying the rules resulted in 0 target repos to look in.

I guess the logic being applied is to get the list of constituents to the starting group (FID) and then straight away intersect with the ordered repo list, rather than resolve any contained groups down into their constituent repos first.

I appreciate this could be considered "by design", but if so then I'd say it's a bit unintuitive, so should at least be clarified in the docs.