• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Create Request
    • None
    • 0
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue Summary

      Currently, the customer lookup handling in Service Desk has the following constraints by design:

      • Customers can be only searchable in the Customer portal if they are members of the Customers list.
      • There are additional conditions that need to be fulfilled, based on the "Customer permissions" settings:
        • A reporter will only be able to search for users who are members of the same organization, if "Other customers in their organization" is set.
        • If you want to grant permission to a reporter to browse through all users who are on the customer list, you need to select "Any customer or organization, by searching in this project". (see attached screenshot)

      The purpose of this feature request is to allow the customers to see other users from the portal (in User Picker fields for example) that are not necessarily customers and without modifying the permissions in the project's "Customer permissions".

      Steps to Reproduce

      • Created a custom field "User Picker" filtered for jira-servicedesk-users group and added it to my IT help Request Type portal.
      • Created some users, only user2 is added to service desk customers group
      • Set the customer permission in my project to "Customers who are added to the project"
      • Added user1 manually to the list of customers in my project to have at least two customers:
      • Log in as user1, try to create a request and add users to the User Picker field.

      Expected Results

      user1 should be able to search for the other users from the portal regardless of the project's "customer permissions" i.g there should be an option to set who is visible from the portal.

      Actual Results

      • Tried to create a request as user1, in the user picker field, it only suggests user2 from the list of users (I am also able to search the admin, but not the other users)
      • Changed the permission in my project to allow Customers who have an account on this Jira site to open requests. Now I have the other users as customers in my project. I tried to create a request as user1, in the user picker field, now it shows the other users:


      Workaround

      For now, the workaround is to loosen the permission to enable "Customers who have an account on this Jira site" to raise requests so that they are considered as customers and will show in the User Picker field in the portal, and use third-party plugins to restrict the creation of the requests for a restricted group.

      Note

      This issue might be related to JSDSERVER-5406 since it addresses user lookup vs customer permissions in JSD.

            [JSDSERVER-6704] Improve the customer lookup function

            Atlassian Update – 5 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 5 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Charlie Jira Service Management, Server & Data Center

            We have a particular use-case where this restriction is impacting us.

            We have a HR Portal where all of the request types should only be created by employees. We have other staff categories (assignees, Member Engineers and Affiliate Engineers) who are not employees. They should not be creating these requests. However, employees need to be able to pick a name of a non-employee.

            Currently, the only way that can work is if I loosen the customer list for that portal which then opens the possibility of the non-employees raising tickets. The only workaround I can use would be a third-party app to hide the visibility of the request types except for employees.

             

            Philip Colmer added a comment - We have a particular use-case where this restriction is impacting us. We have a HR Portal where all of the request types  should only be created by employees. We have other staff categories (assignees, Member Engineers and Affiliate Engineers) who are not employees. They should not be creating these requests. However, employees need to be able to pick a name of a non-employee. Currently, the only way that can work is if I loosen the customer list for that portal which then opens the possibility of the non-employees raising tickets. The only workaround I can use would be a third-party app to hide the visibility of the request types except for employees.  

              Unassigned Unassigned
              mdhahak@atlassian.com Meriem Dhahak
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: