Issue Summary

While populating options for User type attribute Insight/Assets uses different REST API endpoints between Old object schema view vs. New object view showing inconsistent results.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create LDAP connector with jira which imports a few groups and member users
2. Create a User type attribute restricted to any of those imported groups
3. Edit object and click drop down on the User type attribute from the Old object schema view http://<BASE-URL>/secure/ObjectSchema.jspa?id=xx&typeId=yyy&mode=object&objectId=12345 and Edit the same object in the new object view http://<BASE-URL>/secure/insight/assets/XYZ-12345

Expected Results

User sees the same options

Actual Results

• User sees different options:

  Old Object Schema View	New Object view
  REST endpoint: /rest/insight/1.0/user/picker?groups=jira-software-users	REST endpoint: /rest/insight-am/1/users/picker?criteria=&groups=jira-software-users
  Returns 1 user	Returns 4 users

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available