Issue

In tracker’s fields configuration one can bind values of a selectbox to a group of users. This all works fine until the bind is set to the group registered_users. This groups targeting all registered users of the platform it can represent a really large number of users. Currently, there is a check for that in the code that prevents those values to be sent back by the REST API specifically for this group (https://gerrit.tuleap.net/plugins/gitiles/tuleap/+/52d337ad940ed57ff4c1826c86bfccf6711ae306/plugins/tracker/include/Tracker/FormElement/Tracker_FormElement_Field_List_Bind_Users.php#196). This code leads to an issue anywhere this information would be used to fill in the avaible values, for instance in the modal:

Proposed solution

Letting the values be returned by the /api/trackers/:id route might to lead to heavy payloads as well as unusable interfaces overloaded by the available values.

The proposal is not to change the route’s behavior for now and instead change the frontend behavior where needed: If a binding to registered_users is detected, the values from the Tracker’s structure won’t be considered and instead the list picker will be swapped for a Lazybox that will query back the API for user name’s completion