Webhook incorrect payload resulting in inconsistent data for custom field

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 10.3.6, 10.6.0
    • Affects Version/s: 8.13.22, 10.3.2
    • Component/s: Webhooks
    • None
    • 8.13
    • 2
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 17 April 2025

      Dear Customers,

      We're happy to announce that this issue is fixed in the 10.3.6 and 10.6.0 releases. Learn more about the release

      The development team resolved the issue by clearing the cache used by the webhook dispatcher to ensure it did not contain stale data.

      Best regards

      Dino Costantini

      Principal Software Engineer

      Show
      Atlassian Update – 17 April 2025 Dear Customers, We're happy to announce that this issue is fixed in the 10.3.6 and 10.6.0 releases. Learn more about the release The development team resolved the issue by clearing the cache used by the webhook dispatcher to ensure it did not contain stale data. Best regards Dino Costantini Principal Software Engineer

      Issue Summary

      The webhook payload may present incorrect data for custom fields even if the data is correct in the changelog section of the payload.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create some custom fields for date/number/text.
      2. Create a webhook with all trigger options marked for issue.
      3. Trigger the webhook with an existing ticket by editing the custom fields.
      4. Observe the payload is correct in both the changelog and customfield_<number>.
      5. Edit the same webhook removing one of the Issue actions (as example the "worklog changed").
      6. Edit the issue once again ticket by editing the custom fields (can be done multiple times for comparison).
      7. Notice the payload for the customfield_<number> presents incorrect information, but changelog is correct (as images below).

      Expected Results

      Correct data in both changelog and customfield_<number> sections.

      Actual Results

      Correct data in changelog but incorrect in customefield_<number>.

      Workaround

      After restarting all nodes, it is corrected; however, the same erratic behavior is seen if the webhook is changed once again.

        1. WebhookPayloadFailure.png
          123 kB
          Douglas Alves
        2. WebhookPayloadFailure2.png
          140 kB
          Douglas Alves

            Assignee:
            Dino Costantini (Inactive)
            Reporter:
            Douglas Alves (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: