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

      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.

          Form Name

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

            Charlie Marriott made changes -
            Resolution Original: Done [ 17 ] New: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3010994 ] New: JAC Suggestion Workflow 3 [ 3646140 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665092 ] New: JAC Suggestion Workflow [ 3010994 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2322909 ] New: Confluence Workflow - Public Facing v4 [ 2665092 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052799 ] New: JSD Suggestion Workflow - TEMP [ 2322909 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049138 ] New: JSD Suggestion Workflow [ 2052799 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280657 ] New: JSD Suggestion Workflow - TEMP [ 2049138 ]
            jonah (Inactive) made changes -
            Description Original: 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.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-393].
              {panel}

            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.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-393 [ JSDCLOUD-393 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-cloud New: affects-cloud affects-server

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

                Created:
                Updated:
                Resolved: