• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.0-OD-04
    • 1.2.0.2
    • SLA

      When we retrieve and issue using rest api values for the SLA fields are not correct.
      Here is a snippet from the response:

      "customfield_10202":"com.atlassian.servicedesk.internal.sla.model.SLAValue@f245367","customfield_10201":"com.atlassian.servicedesk.internal.sla.model.SLAValue@19df96f5",
      

      It would be very useful if you just return the JSON value on the database.

          Form Name

            [JSDSERVER-346] SLA Fields' values are not return correctly in JIRA rest

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304855 ] New: JAC Bug Workflow v3 [ 3125490 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058771 ] New: JSD Bug Workflow v5 - TEMP [ 2304855 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056121 ] New: JSD Bug Workflow v5 [ 2058771 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1955548 ] New: JSD Bug Workflow v5 - TEMP [ 2056121 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1614753 ] New: JSD Bug Workflow v5 [ 1955548 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1602012 ] New: JSD Bug Workflow v4 [ 1614753 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1398139 ] New: JSD Bug Workflow v2 [ 1602012 ]
            Owen Sanico [Administrative Account] made changes -
            Workflow Original: TTT: Simple Issue Tracking Workflow [ 624988 ] New: JSD Bug Workflow [ 1398139 ]

            Midori added a comment -

            A work around could be exporting your data to Excel sheets and then use that directly or its in CSV format for data integration purposes.

            Better Excel Plugin correctly exports the SLA fields (and even applies coloring rules to that, albeit this may be insignificant in this use case ) and you can even apply Excel features to manipulate that (as a Transform part of a full ETL process). Learn more about this

            Another tool that enchances this is the Excel Automation Plugin which can do this transformation periodically. (We actually transform JIRA issues to another system this way.)

            Midori added a comment - A work around could be exporting your data to Excel sheets and then use that directly or its in CSV format for data integration purposes. Better Excel Plugin correctly exports the SLA fields (and even applies coloring rules to that, albeit this may be insignificant in this use case ) and you can even apply Excel features to manipulate that (as a Transform part of a full ETL process). Learn more about this Another tool that enchances this is the Excel Automation Plugin which can do this transformation periodically . (We actually transform JIRA issues to another system this way.)

              Unassigned Unassigned
              atlassian155 Kerem Caglar [Solveka]
              Affected customers:
              14 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: