• 1
    • 19
    • 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.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      We would like the ability to select whether or no to have a Service Desk that is unrestricted appear on the list of Service Desks on the Help Center. It may be additional beneficial to have the ability to create multiple Help Centers and assign Service Desks to the appropriate Help Center. An example of the reasoning for this would be a grouping of Service Desk for internal users and external users and/or for product brand grouping.

            [JSDSERVER-1702] The option to exclude a Service Desk Customer Portal from the Help Center

            Hi, 

            I am currently trying to hide a project from our customer portal, where the issues are automatically created through scripts using the Jira Rest API. Later in the Process some users might have to approve these issues.

            For all using Jira Data Server 10 versions, the proposed Plugin will block the load of the customer portal page.

            There is currently no workaround on the market for this feature. 

            I hope Atlassian will reconsider prioritizing this Suggestion, considering also that Jira Cloud offers the option

            Below you can find the response from the vendor

            "

            The issue is related to changes in Jira v10 versions, and the source of this problem is the interference between Jira and our Extension for JSM. Based on our analysis, we have observed that when the Extension is enabled, Jira sends a broken request, which results in the portal being stuck in an infinite loading state. While our application does not modify this request in any way, the issue only occurs when the Extension is active.

            Unfortunately, we do not have an official release with the fix yet. We are actively working with the Atlassian team to provide a comprehensive fix for this problem.

            As a temporary solution, could you please disable the following two modules under Extension for the JSM plugin [Manage apps tab in Jira Settings]:

            • Servlet-filter: Service desk refresh
            • Servlet-filter: Service desk model

            For a few of our customers, that operation helped. Please note that these modules are related to the Visibility feature, so disabling them will temporarily prevent that functionality from working.

            "

            Alexandra

            Alexandra Neciov added a comment - Hi,  I am currently trying to hide a project from our customer portal, where the issues are automatically created through scripts using the Jira Rest API. Later in the Process some users might have to approve these issues. For all using Jira Data Server 10 versions, the proposed Plugin will block the load of the customer portal page. There is currently no workaround on the market for this feature.   I hope Atlassian will reconsider prioritizing this Suggestion, considering also that Jira Cloud offers the option Below you can find the response from the vendor " The issue is related to changes in Jira v10 versions, and the source of this problem is the interference between Jira and our Extension for JSM. Based on our analysis, we have observed that when the Extension is enabled, Jira sends a broken request, which results in the portal being stuck in an infinite loading state. While our application does not modify this request in any way, the issue only occurs when the Extension is active. Unfortunately, we do not have an official release with the fix yet. We are actively working with the Atlassian team to provide a comprehensive fix for this problem. As a temporary solution, could you please disable the following two modules under Extension for the JSM plugin [Manage apps tab in Jira Settings] : Servlet-filter: Service desk refresh Servlet-filter: Service desk model For a few of our customers, that operation helped. Please note that these modules are related to the Visibility feature, so disabling them will temporarily prevent that functionality from working. " Alexandra

            Hi,

            You can restrict visibility of customer portal to Jira groups using our app [Extension for Jira Service Desk|https://marketplace.atlassian.com/apps/1212161/extension-for-jira-service-desk?hosting=server&tab=overview.]

             

            Kate

            Katarzyna Pawlak [Deviniti] added a comment - Hi, You can restrict visibility of customer portal to Jira groups using our app [Extension for Jira Service Desk| https://marketplace.atlassian.com/apps/1212161/extension-for-jira-service-desk?hosting=server&tab=overview .]   Kate

            We need something similar here as well.  We use SD for our internal support teams.  We'd also like to use Service Desk for our customer-facing support.  We'd need a way to have two separate Help Center portals then.  One with the two internal SD projects, and one with external customer facing projects.  It would be great if we could assign a SD project to a Help Center portal to separate those two worlds...  -Nicole

            Nicole Hushka added a comment - We need something similar here as well.  We use SD for our internal support teams.  We'd also like to use Service Desk for our customer-facing support.  We'd need a way to have two separate Help Center portals then.  One with the two internal SD projects, and one with external customer facing projects.  It would be great if we could assign a SD project to a Help Center portal to separate those two worlds...  -Nicole

            Dario B added a comment -

            I confirm that in case you want public sign-up enabled there is no way to restrict the customers' portals visibility (other than hiding them from the Help Center)

            Dario B added a comment - I confirm that in case you want public sign-up enabled there is no way to restrict the customers' portals visibility (other than hiding them from the Help Center)

            Dario B added a comment -

            andy.holvoet: I am afraid in that case the only option is to hide the other service desks... However, let me look into this and get back to you

            Cheers,
            Dario

            Dario B added a comment - andy.holvoet : I am afraid in that case the only option is to hide the other service desks... However, let me look into this and get back to you Cheers, Dario

            aholvoet added a comment - - edited

            @Dario Bonotto [Atlassian] What do you suggest when users can register anonymously?

            aholvoet added a comment - - edited @Dario Bonotto [Atlassian] What do you suggest when users can register anonymously?

            Dario B added a comment - - edited

            I believe that restricting customers access to specific service desks projects only (and therefore to specific customers portals only) can be the best way to solve this. Indeed, once this has been configured, each customer will only see the customer portals he has access to in the help center.

            For details please see:

            This does not apply in case your users are registering anonymously.

            Dario B added a comment - - edited I believe that restricting customers access to specific service desks projects only (and therefore to specific customers portals only) can be the best way to solve this. Indeed, once this has been configured, each customer will only see the customer portals he has access to in the help center. For details please see: How to restrict customers access to specific projects only in JIRA Service Desk Cloud This does not apply in case your users are registering anonymously.

              Unassigned Unassigned
              629c61e31d32 Sam Ware
              Votes:
              31 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated: