Uploaded image for project: 'Compass'
  1. Compass
  2. COMPASS-67

Users with basic access cannot be selected in search filters for Compass using the custom field for user type.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • Global - Search
    • None

      Issue Summary

      Custom fields of type "user" do not function correctly in the search filters on the components page. Users with the "basic user" role cannot be filtered or selected.

      Steps to Reproduce

      1. Create a custom field of type user.
      1. In a component that has this custom field, add a user with the "basic user" role.
      1. Access the "Components" page and add the previously created custom field as a filter.
      1. Note that the user who has basic user access to Compass is not listed for selection.

      Expected Results

      Users with the "basic user" role should be available for selection in the filter options on the Components page.

      Actual Results

      It is expected that all users who have access to Compass are in the list to be used in the filter, since it is possible to select the same in the field within the components.

      Workaround

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

            [COMPASS-67] Users with basic access cannot be selected in search filters for Compass using the custom field for user type.

            Moinul added a comment -

            Moinul added a comment - threw a bug in the backlog https://softwareteams.atlassian.net/browse/COMPASS-23751

            Moinul added a comment -

            I did some digging on this and seems like there is a bug on our search code. We likely aren't setting the right request parameters to search OR the user recommendation service is not correctly returning the data. Though after taking a quick look at their API, it seems setting the `productKey` to `compass` and `productAccessPermissionIds` in the query to include `basic` role should do the trick, doesn't look like it does. I have thrown a ticket in our backlog for further investigation

             

            One quick remedy can be what we do in our teams page (when you invite users to the product with +create team button) which sets the productKey to be `people` but this will likely search across all the users on the site even if they don't have access to Compass.

             

             

            context: {
              ...
              productKey: 'people',
              ...
            }, 

             

             

            Moinul added a comment - I did some digging on this and seems like there is a bug on our search code . We likely aren't setting the right request parameters to search OR the user recommendation service is not correctly returning the data. Though after taking a quick look at their API, it seems setting the `productKey` to `compass` and `productAccessPermissionIds` in the query to include `basic` role should do the trick, doesn't look like it does. I have thrown a ticket in our backlog for further investigation   One quick remedy can be what we do in our teams page (when you invite users to the product with +create team button) which sets the productKey to be `people` but this will likely search across all the users on the site even if they don't have access to Compass.     context: { ... productKey: 'people' , ... },    

              mhossain@atlassian.com Moinul
              4c2ff7ed7f76 Kelvin T
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated: