Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-26027

After enabling dark feature for asynchronous WebHooks and restarting Jira, webhook payloads fail to send Parent Link data

    • 8.2
    • 1
    • Severity 3 - Minor
    • 1
    • Hide
      Atlassian Update – 10 July 2024

      Dear Customers,

      Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog.

      Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

      Best regards

      Daniel Dudziak
      Principal Software Engineer

      Show
      Atlassian Update – 10 July 2024 Dear Customers, Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Daniel Dudziak Principal Software Engineer

      Issue Summary

      After enabling the dark feature for async webhook and restarting Jira, webhook payloads fail to send Parent Link data, especially when we have new hierarchy level (Admin > Manage apps > Hierarchy configuration) and one of this level issue set as parent.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Setup a webhook destination in Jira
        • Admin > System > Webhooks
      2. Enable the webhook debug to 
        • Admin > System > Logging and Profiling > Set com.atlassian.webhooks with debug verbose log
      3. Fire an event that sends a webhook payload and observe the result.
      4. In Jira software enable the async webhook dark feature
        • In jiraurl/secure/admin/SiteDarkFeatures!default.jspa add/enable the "com.atlassian.jira.webhookEventsAsyncProcessing.enabled" dark feature
      5. Restart the Jira instance
      6. Reproduce steps 2 and 3 and observe the results. 

      Expected Results

      The webhook payload is completely populated.

      Actual Results

      The custom field "Parent Link" is not populated as expected.

      Below we have the payload when:

      • sync webhook is being used (without the async dark feature and Jira restarted):
        (...)
        event {7}
        body {5}
        issue{4}
        fields{81}
        ...
        created: 2024-03-25T20:38:01.294-0300
        creator{8}
        customfield_10000{summaryBean=com.atlassian.jira.plugin.devstatus.rest.SummaryBean@5067ce07[summary={pullrequest=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@292e35ab[overall=PullRequestOverallBean{stateCount=0, state='OPEN', details=PullRequestOverallDetails{openCount=0, mergedCount=0, declinedCount=0}},byInstanceType={}], build=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@33b96b37[overall=com.atlassian.jira.plugin.devstatus.summary.beans.BuildOverallBean@6be28386[failedBuildCount=0,successfulBuildCount=0,unknownBuildCount=0,count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], review=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@69287661[overall=com.atlassian.jira.plugin.devstatus.summary.beans.ReviewsOverallBean@37e44df5[stateCount=0,state=<null>,dueDate=<null>,overDue=false,count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], deployment-environment=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@4ffc68ed[overall=com.atlassian.jira.plugin.devstatus.summary.beans.DeploymentOverallBean@30fd2c27[topEnvironments=[],showProjects=false,successfulCount=0,count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], repository=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@1accdf27[overall=com.atlassian.jira.plugin.devstatus.summary.beans.CommitOverallBean@fd2b26e[count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], branch=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@23c51879[overall=com.atlassian.jira.plugin.devstatus.summary.beans.BranchOverallBean@7a009432[count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}]},errors=[],configErrors=[]], devSummaryJson={"cachedValue":{"errors":[],"configErrors":[],"summary":{"pullrequest":{"overall":{"count":0,"lastUpdated":null,"stateCount":0,"state":"OPEN","details":{"openCount":0,"mergedCount":0,"declinedCount":0,"total":0},"open":true},"byInstanceType":{}},"build":{"overall":{"count":0,"lastUpdated":null,"failedBuildCount":0,"successfulBuildCount":0,"unknownBuildCount":0},"byInstanceType":{}},"review":{"overall":{"count":0,"lastUpdated":null,"stateCount":0,"state":null,"dueDate":null,"overDue":false,"completed":false},"byInstanceType":{}},"deployment-environment":{"overall":{"count":0,"lastUpdated":null,"topEnvironments":[],"showProjects":false,"successfulCount":0},"byInstanceType":{}},"repository":{"overall":{"count":0,"lastUpdated":null},"byInstanceType":{}},"branch":{"overall":{"count":0,"lastUpdated":null},"byInstanceType":{}}}},"isStale":false}}
        ...
        customfield_10108: SBP-1
        (...)
        

        The custom field 10108 relates to Parent Link

      • async webhooks is used and restart your Jira (before restart it will not fail)
        event{7}
        body{5}
        issue{4}
        fields{81}
        ...
        created: 2024-03-25T20:33:53.299-0300
        creator{8}
        customfield_10000:{}
        customfield_10100: null
        ...
        customfield_10108: null
        (...)
        

        The custom field 10108 relates to Parent Link. Note the custom field 10000 ("Development") did not present data as well.

      Workaround

      Disable async webhooks and restart Jira:

      • Go to jiraurl/secure/admin/SiteDarkFeatures!default.jspa and disable the "com.atlassian.jira.webhookEventsAsyncProcessing.enabled" dark feature
      • Restart the instance.

       The workaround doesn't work in Jira 10 as Webhooks work in async mode there by default, even without  com.atlassian.jira.webhookEventsAsyncProcessing.enabled dark feature enabled.

          Form Name

            [JSWSERVER-26027] After enabling dark feature for asynchronous WebHooks and restarting Jira, webhook payloads fail to send Parent Link data

            Kunal Kanojia made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 995477 ]
            Jira Server Release Automation Bot[ADM-107524] made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Rajshri made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 964129 ]
            Rajshri made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 964059 ]
            Marc Dacanay made changes -
            Labels Original: ACE-5613 ltsr New: ACE-5613
            Kunal Kanojia made changes -
            Fix Version/s New: 10.2.0 [ 108819 ]
            Kunal Kanojia made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Kunal Kanojia made changes -
            Assignee New: Amith Vikram Vemaganti [ 8d330667a844 ]
            Amith Vikram Vemaganti made changes -
            Status Original: Short Term Backlog [ 12074 ] New: In Progress [ 3 ]
            Amith Vikram Vemaganti made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 948858 ]

              8d330667a844 Amith Vikram Vemaganti
              b99328de92bd Douglas Alves (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: