Enable system to deal with more than 250 users

.Thank you for submitting this enhancement to list more than 250 names in the People Picker. We've reviewed your request and have decided to decline it. The People Picker is designed to quickly filter the list of users by entering text in the Name box. We determined that showing more names would increase the effort of finding the desired person due to manually searching a long list, and it could potentially impact performance due to loading a large list of unfiltered names.
We appreciate your suggestion and hope this information will provide a better experience of using the People Picker.

We also opened a ticket about this and since it is a behavior of the people picker all over the ELM.
This is the answer we received: "There was a defect that was raised by Jim (my colleague) in the previous case for the issue you reported, so i reached out to the developer who was handling the defect and he replied:

It was targeted to be fixed in Document builder version 703 but the defect was rejected as all ELM products follow the same limit so it cant be changed.

"People picker is configured to fetch only 250 records at a time and it's consistent across ELM applications, it is better not to change the behaviour only in Document Builder.""

If you have a lot of users in the system let's say 400. Than only the first 250 users (alphabetic order) are able e.g. to pick their name when creating a WI. This is true all over the application. Another example is picking a report owner in the Document Builder. We experienced this in multiple areas and it is a nasty limitation for bigger companies.

Thank you for requesting the change to add owners and permissions for users later in the alphabet than the first 250 users. We have two questions we need answered to evaluate this request:

1. Can you provide the steps to re-produce this behavior? It's unclear what the relationship is between letters in the alphabet and the limit of 250 users.
2. Have you contacted Support and investigated this as a defect? Depending on the steps in #1, this may be a defect. If you haven't contacted Support yet we recommend you do so and they can open a defect if appropriate. If you've already contact Support on this issue please provide the case ID to help us respond to the RFE.

Thank you.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - ELM Common Services
Component - Unassigned
Operating system - Multiple
Source - None

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Requirements Management DOORS Next (formerly DOORS Next Generation- DNG)
Component - Usability
Operating system - Multiple
Source - None