Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3387

As an admin, ability to specify which columns show in Service Desk requests page

XMLWordPrintable

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

      Atlassian Update – 10 December 2021

      Hi everyone,

      Thank you for your interest in this issue.

      As a part of Jira Service Management Data Center 4.21 we have released column configuration on the Help center’s request list view. This allows Jira admins to select the columns that they would like to appear in their customer's requests list. It also allows customers to configure and order the columns.

      The available fields are type, reference, summary, status, service project, requester, created date, updated date, due date, assignee and priority.

      Please refer to our documentation to learn how to configure the requests list.

      Kind regards,

      Charlie Marriott
      Jira Service Management, Data Center & Server

      Problem Definition

      In Service Desk Customer Portal, the Requests page only shows a few columns by default.

      Suggested Solution

      Examples would be Created Date, Updated Date. These aren't fields that show in the same way as other fields, but the users would like some way to display this information in the Customer Portal

        1. Screen Shot 2016-02-08 at 11.08.08.jpg
          Screen Shot 2016-02-08 at 11.08.08.jpg
          40 kB

              cmarriott Charlie Marriott
              smackie@atlassian.com Shannon S
              Votes:
              480 Vote for this issue
              Watchers:
              194 Start watching this issue

                Created:
                Updated:
                Resolved: