Improve dynamic filtering for lookup relationship fields on tickets

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

Earlier this year, we got this lovely feature: https://support.zendesk.com/hc/en-us/articles/6941856507930-Announcing-dynamic-filtering-for-lookup-relationship-fields-on-tickets - but it has a gap.

Suppose I have a custom object called Products that will show which products or entitlements a customer has purchased. This custom object has a lookup relationship field called “Account Name” that looks up to the Organization.

Organization: ACME inc 

Product: Product A

Product: Product C

Product: Product D

When a requester submits a ticket, we want them to be able to select from the above products that their organization has purchased. So we create a ticket lookup relationship to the Product custom object, with a filter for Account Name = (dynamic filter for Ticket Organization)

PROBLEM: This dynamic filter doesn't work on the new request page when a customer creates a ticket. It is looking for Ticket Organization, but the Ticket does not exist yet, so it doesn't return any products. 

What we need is a dynamic filter for Requester/User Organization, so that a Requester on the New Request page can use this ticket field to see only the products their Org has purchased.

What problem do you see this solving? (1-2 sentences) 

This would allow for an improved user experience where customers can select from only the products or entitlements their organization has purchased. 

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

This affects nearly every ticket. We expect the customer to provide us this data point in a text field today which makes for bad data, inconsistent reporting and requires agents to spend extra time double checking the customers' products/entitlements. 

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

See above

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

The dynamic filter for User Organization will allow any user from the above example org to submit a new request, and select only Product A, C or D. They would not see other products that are not relevant to them that they haven't purchased.