Comment 1 for bug 1825076

Comment 1. Yes, the Org unit selector overlaps the No subscriptions are owned message, but I am not sure that is a problem.

Comment 2. Yes, when you select a choice on the Org tree and click New subscription, the resulting subscription does not necessarily appear at the level you selected on the Org tree (but it might).

That said, it isn't defaulting to the top of the Org tree, i.e., select BR1 and it defaults to CONS as the top of the Org tree. It's defaulting to your login branch. I had the same result as above when testing on Blake's test server during this Feedback Fest (2/11/2021). I believe that demo login puts you at the CONS level. When I selected CONS and clicked New subscription, it created it as CONS.

On my library's own system (3-4-5), I always select the top of the Org tree for our subscriptions, but it always creates the new subscriptions at my branch level and I have to change it to the "Consortium" level.

I agree, it isn't what I would expect. I would expect that choosing an Org unit and selecting New subscription, it would create said subscription at the level I had just selected, not my home branch.