Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10006

As an Admin I want to allow anonymous user to be able to view and select options in an Assets Objects field in the Help Center (Portal)

    • 61
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      At the moment, when the JSM Customer Portal set to public , customer will create issue as anonymous. As anonymous, users have no roles in the system, Insight Object custom field cannot show them the objects since they are not recognized as users by Insight.

      Suggested Solution

      It would be nice to have the option to show allow anonymous user to select Insight Object from the Insight Object custom field type.

      Workaround

      1. Create a select list custom field and add all the objects as the data.
      2. Then, create automation to update the Insight object custom field according to the custom field value.

            [JSDCLOUD-10006] As an Admin I want to allow anonymous user to be able to view and select options in an Assets Objects field in the Help Center (Portal)

            A whole lot of use cases for Jira Service Management is waiting for this. Why not allow for anonymous view permissions to asset fields for portal users AND view permissions into asset schemas for all users with any product license.

            Lisa Förstberg added a comment - A whole lot of use cases for Jira Service Management is waiting for this. Why not allow for anonymous view permissions to asset fields for portal users AND view permissions into asset schemas for all users with any product license.

            Any update on this? The benefit of working with Assets/granting anonymous access to customers is kind of squandered by this missing feature.

            Almuth Boehme [Communardo] added a comment - Any update on this? The benefit of working with Assets/granting anonymous access to customers is kind of squandered by this missing feature.

            The worst part is that they now have synced Compass components to Jira Assets, but we still can't expose these fields. So we can't really use compass components across all projects as intended.

            Luka Hummel - codefortynine added a comment - The worst part is that they now have synced Compass components to Jira Assets, but we still can't expose these fields. So we can't really use compass components across all projects as intended.

            This would significantly improve my workflow as well.

            Dylan Tisdall added a comment - This would significantly improve my workflow as well.

            Any update on this topic? We are in the same situation.

            G. De Fazio added a comment - Any update on this topic? We are in the same situation.

            This is a huge blocker for us right now. we allow anonymous users to create tickets in out JSM portal. we need this type of insight field to be required so that they can select items from out insight schema and then we can route our JSM tickets accordingly. 

            Wade Hephner added a comment - This is a huge blocker for us right now. we allow anonymous users to create tickets in out JSM portal. we need this type of insight field to be required so that they can select items from out insight schema and then we can route our JSM tickets accordingly. 

              90325da67d46 Mohamed Hassan
              bd0e47de2684 Yuri Moura (Inactive)
              Votes:
              57 Vote for this issue
              Watchers:
              40 Start watching this issue

                Created:
                Updated: