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

Allow customer portal users to see Issue Key in "My Requests"

    XMLWordPrintable

Details

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

    Description

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

      On the "My Requests" screen in the customer portal, users can only see description and status. This is quite limiting, especially where a user has a number of issues open and needs to discuss with support.

      Some of our clients have 20+ issues open, and want to run through their list with a support rep - only having the description to go on makes running through the list quite tedious.

      As a minimum, the Jira Issue key should be displayed alongside each issue.

      But (better still) a portal administrator should be able to choose what fields to show/hide on the "My requests" view, as you can with filters in in Issue Navigator.

      Attachments

        Issue Links

          is duplicated by

          Suggestion - JSDCLOUD-2285 Show Ticket Numbers on Customer Portal

          • Closed
          is related to

          Suggestion - JSDCLOUD-1663 Allow customers to filter My Requests

          • Closed

          Suggestion - JSDSERVER-393 Allow customer portal users to see Issue Key in "My Requests"

          • Closed
          relates to

          Suggestion - JSDCLOUD-1330 Showing Issue Key in the Customer Portal

          • Closed

          Activity

            People

              Unassigned Unassigned
              158c6ea5fc5c Mark Love
              Votes:
              61 Vote for this issue
              Watchers:
              41 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: