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

Ability to Add more Columns / custom fields to custom report drill-down table

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 0
    • 4
    • 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.

      Summary

      Currently the custom report displays fixed columns with limited information. (key, request summary, reporter, assignee, request type and status)

      Suggestion

      It should be possible to customize the report with more columns e.g. component, insight custom field (CMDB / service category), date, etc.

          Form Name

            [JSDSERVER-4448] Ability to Add more Columns / custom fields to custom report drill-down table

            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 4
            Marc Dacanay made changes -
            Labels New: ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 980935 ]

            Jesse Rapczak added a comment -

            Please add this feature!! So surprised it is missing. 

            Jesse Rapczak added a comment - Please add this feature!! So surprised it is missing. 
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0

            john.clark@lva.virginia.gov added a comment -

            We also require this. We moved to JSM last year from another ticketing system, and were very surprised to find this missing from the reporting.

            john.clark@lva.virginia.gov added a comment - We also require this. We moved to JSM last year from another ticketing system, and were very surprised to find this missing from the reporting.
            SET Analytics Bot made changes -
            UIS New: 1
            Charles Trilha (Inactive) made changes -
            Description Original: {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-4448].
              {panel}

            h3. Summary
            Currently the custom report displays fixed columns with limited information. (key, request summary, reporter, assignee, request type and status)

            h3.Suggestion
            It should be possible to customize the report with more columns e.g. componente, insight custom field (CMDB / service category), date, etc.             		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-4448].
              {panel}

            h3. Summary
            Currently the custom report displays fixed columns with limited information. (key, request summary, reporter, assignee, request type and status)

            h3.Suggestion
            It should be possible to customize the report with more columns e.g. component, insight custom field (CMDB / service category), date, etc.

            Nick Green added a comment -

            Our company requires this as well.

            Thanks,
            Nick

            Nick Green added a comment - Our company requires this as well. Thanks, Nick

            Rebecca R. Tate added a comment -

            I've also had this request from VP of Infrastructure, specifically around metrics for SLAs.  It's actually becoming a go/no go type of decision since we need this for basic SLA metrics and reporting.

            Rebecca R. Tate added a comment - I've also had this request from VP of Infrastructure, specifically around metrics for SLAs.  It's actually becoming a go/no go type of decision since we need this for basic SLA metrics and reporting.

              Unassigned Unassigned
              4e81381d415c Tim Eddelbüttel
              Votes:
              21 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: