Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-72491

Sending a issue update webhook on a comment operations, the updated field is not up-to-date

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 9.7.0, 9.4.7
    • 8.5.13, 8.17.0, 8.20.12
    • Webhooks
    • None
    • 8.05
    • 2
    • Severity 3 - Minor
    • 3
    • Hide
      Atlassian Update – 23 February 2023

      Hi everyone,

      I'm happy to announce that fix for this issue will be release in the upcoming Jira 9.7.0. According to our policy, after proper soaking time this fix will be backported to Jira LTS versions: 9.4 and 8.20. You can expect it to happen in Q2 2023.

      Thank you,
      Michał Błajet
      Jira Developer

      Show
      Atlassian Update – 23 February 2023 Hi everyone, I'm happy to announce that fix for this issue will be release in the upcoming Jira 9.7.0. According to our policy, after proper soaking time this fix will be backported to Jira LTS versions: 9.4 and 8.20. You can expect it to happen in Q2 2023. Thank you, Michał Błajet Jira Developer

    Description

      Issue Summary

      When sending a issue update webhook on a comment operations (create/edit/delete), the updated field for the issue is not up-to-date.

      After the webhook is sent, we can see the updated is actually updated.

      Note: for webhooks triggered from issue fields updated, the updated field has the correct value.

      Steps to Reproduce

      1. Set up a webhook for when the issue is updated
      2. Enable com.atlassian.webhooks as DEBUG, to see the payload in the logs
      3. Add/edit/delete a comment in an issue

      Expected Results

      The updated field for the issue has the same date as the last updated comment.

      Actual Results

      The updated field for the issue has the value from before the comment was added/edited/deleted.

      Workaround

      Instead of using the updated field, please use the timestamp when:

      • "webhookEvent": "jira:issue_updated"
        AND
      • issue_event_type_name is like issue_comment*

      It might not be a 100% match with the updated field, but it's a valid approximation.

      Attachments

        Issue Links

          Activity

            People

              cb173a7ca7c0 Michał Błajet
              5fb7769fcbc7 Allan Gandelman
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: