Webhook POST Triggered from Customer Portal Doesn't Include 'changelog' Node

XMLWordPrintable

    • 3
    • Severity 3 - Minor
    • 1

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

      Summary

      When an issue_updated webhook event is triggered by an action in Customer Portal, the posted JSON misses the 'changelog' node.

      Steps to Reproduce

      1. Set up a webhook to be triggered at 'Issue updated' event, and with a JQL covering a project with Service Desk enabled.
      2. In Customer Portal view of an issue covered by the webhook's JQL, add an attachment, with or without a comment.
      3. Observe the JSON posted at the issue update.

      Expected Results

      The POST body includes the 'changelog' node with the information about new attachment:

      "changelog": {
          "id": "11111",
          "items": [
            {
              "field": "Attachment",
              "fieldtype": "jira",
              "from": null,
              "fromString": null,
              "to": "11111",
              "toString": "image.png"
            }

      Actual Results

      The POST is missing the 'changelog' details, only the information about the new comment is distinguished.
      They 'changelog' information is only included in POSTs triggered by actions in JIRA Issue View or Service Desk agent views.

      Notes

      To see the details of Webhooks posts in JIRA logs: in JIRA Admin > System > Logging & Profiling add the package com.atlassian.webhooks witht the DEBUG level of logging.

        1. NSE4_FGT-6.0-exam-dumps.pdf
          486 kB
          Alan Lewis
        2. 70-333-exam-dumps.pdf
          1.45 MB
          Rose Short

            Assignee:
            Tomasz Zasada
            Reporter:
            Dobroslawa Wierzbicka (Inactive)
            Votes:
            16 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: