• Icon: Bug Bug
    • Resolution: Tracked Elsewhere
    • Icon: Low Low
    • None
    • None
    • SLA
    • None

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

      When user search any issue from Issue Navigator, they can see the Time waiting for support and Time to resolution values as per issue-navi.png screenshot.
      Export issues to Excel also able to show the Time waiting for support and Time to resolution values as per xls.png screenshot.
      However, the data is not shown in XML format as per xml2.png screenshot.
      Finding:
      ServiceDesk Add-on v1.2.6.1
      Locked Custom Fields (locked-vs-unlocked.png) able to show the values in XML format if compare xml1.png with xml2.png.

        1. xml2.png
          48 kB
          Ian Dick
        2. xml1.png
          22 kB
          Ian Dick
        3. xls.png
          26 kB
          Ian Dick
        4. locked-vs-unlocked.png
          11 kB
          Ian Dick
        5. issue-navi.png
          23 kB
          Ian Dick

          Form Name

            [JSDSERVER-581] Service Desk SLA Custom Field values doesn't show in XML format

            Adven made changes -
            Link New: This issue relates to JSDCLOUD-9455 [ JSDCLOUD-9455 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305164 ] New: JAC Bug Workflow v3 [ 3125688 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059098 ] New: JSD Bug Workflow v5 - TEMP [ 2305164 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056495 ] New: JSD Bug Workflow v5 [ 2059098 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956066 ] New: JSD Bug Workflow v5 - TEMP [ 2056495 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1616002 ] New: JSD Bug Workflow v5 [ 1956066 ]
            jonah (Inactive) made changes -
            Description Original: When user search any issue from Issue Navigator, they can see the Time waiting for support and Time to resolution values as per issue-navi.png screenshot.
            Export issues to Excel also able to show the Time waiting for support and Time to resolution values as per xls.png screenshot.
            However, the data is not shown in XML format as per xml2.png screenshot.
            Finding:
            ServiceDesk Add-on v1.2.6.1
            Locked Custom Fields (locked-vs-unlocked.png) able to show the values in XML format if compare xml1.png with xml2.png.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-581].
              {panel}

            When user search any issue from Issue Navigator, they can see the Time waiting for support and Time to resolution values as per issue-navi.png screenshot.
            Export issues to Excel also able to show the Time waiting for support and Time to resolution values as per xls.png screenshot.
            However, the data is not shown in XML format as per xml2.png screenshot.
            Finding:
            ServiceDesk Add-on v1.2.6.1
            Locked Custom Fields (locked-vs-unlocked.png) able to show the values in XML format if compare xml1.png with xml2.png.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-581 [ JSDCLOUD-581 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1603197 ] New: JSD Bug Workflow v4 [ 1616002 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1399057 ] New: JSD Bug Workflow v2 [ 1603197 ]

              Unassigned Unassigned
              idick Ian Dick
              Affected customers:
              5 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: