"Project Manager" and "Assigned To" fields are populated with all Storm People, and not merely those in the host organization

Hi! Apologies if this is a duplicate; I searched a bit and couldn't find anything.

In Storm Project, the Assigned To and Project Manager fields list all people who have a Storm Person record. At least for Project Manager, the options should be limited to people only within the relevant host organization. Failing that, there should be an option in the Storm Project config screen to limit those fields or not (I can understand why enabling those for all people might be useful, but I can imagine quite a number of usage cases where it would not be, and just encumber the dropdown -- my project creates a new Storm Person record for each client, resulting in dropdowns that are massive.)

The "compromise" way to fix this issue would be to replace those dropdowns with autocomplete fields, in my mind -- at least with those, you wouldn't have a dropdown that fills a sizeable portion of the screen once there's a number of Storm People. Frankly, using dropdowns for the Storm Person or Storm Organization reference fields seems a little antiquated anyway... Look at what Noderelationships does with autocomplete fields for an idea about how to really increase usability within Storm in the vein I'm speaking (I.e., "any time a relationship field exists -- Storm Organization inside a Storm Project, for instance -- give users the ability to add a new organization/person/project/whatever via a modal window, without leaving the page.")

Thoughts?