Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-60518

WebHooks not firing when the event triggered is Workflow post function

XMLWordPrintable

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

      We need to transfer the issue status to the external system, so we've made up the workflow with the "trigger a webhook post function". The webhook should only work with transitions, so no issue events are selected.

      It works unstable - sometimes webhook fires immediately after the transition and all the reauired info is posted in the external system.
      Sometimes it works with the time delay (various time intervals).
      Sometimes it doesnt fire at all.

      It is only logged when the webhook was sent successfuly.
      We've tried all the options from https://jira.atlassian.com/browse/JRA-41388, but all connections are ok.

      Are there any other suggestions of the possible reason of the problem?

            [JRACLOUD-60518] WebHooks not firing when the event triggered is Workflow post function

            Bartosz Robakowski made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Bartosz Robakowski added a comment - - edited

            Hello everyone,

            We appreciate your feedback and comments.

            We've decided to close this bug, as we can no longer reproduce it using the initial bug report. The webhook is correctly sent if we set it up using the following steps:

            1. Register and enable a new Jira admin webhook with no events selected and a valid URL (that does not point to the Jira Automation).
            2. Assign the new webhook to a post function in a transition in a workflow and publish changes in the workflow.
            3. Trigger the transition.
               

            We are aware of different bugs affecting the webhook delivery on the issue transition that were incorrectly assigned to this bug:

            If you think the initial bug still exists, please raise a new support ticket so we can investigate it.

            Bartosz Robakowski added a comment - - edited Hello everyone, We appreciate your feedback and comments. We've decided to close this bug, as we can no longer reproduce it using the initial bug report. The webhook is correctly sent if we set it up using the following steps: Register and enable a new Jira admin webhook with no events selected and a valid URL (that does not point to the Jira Automation). Assign the new webhook to a post function in a transition in a workflow and publish changes in the workflow. Trigger the transition.   We are aware of different bugs affecting the webhook delivery on the issue transition that were incorrectly assigned to this bug: If you want to use the  incoming Webhooks Trigger for Atlassian Automation Rules in the post function, please see the workarounds mentioned in the Add Support for X-Automation-Webhook-Token Header in Native Webhooks . Changing the default event fired by 'Fire Event Function' post function to a different system event prevents webhook from being sent or sends incorrect webhook .   If you think the initial bug still exists, please raise a new support ticket so we can investigate it.
            SET Analytics Bot made changes -
            UIS Original: 65 New: 52
            Maciej Stanuch made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1006170 ]
            SET Analytics Bot made changes -
            Support reference count Original: 28 New: 27
            SET Analytics Bot made changes -
            UIS Original: 67 New: 65
            Bartosz Robakowski made changes -
            Link New: This issue is related to JRACLOUD-83784 [ JRACLOUD-83784 ]
            SET Analytics Bot made changes -
            UIS Original: 68 New: 67
            SET Analytics Bot made changes -
            UIS Original: 67 New: 68
            SET Analytics Bot made changes -
            UIS Original: 66 New: 67

              Unassigned Unassigned
              d1ea29b53423 Наталия Ицкович
              Affected customers:
              77 This affects my team
              Watchers:
              74 Start watching this issue

                Created:
                Updated:
                Resolved: