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

Having a custom field that no longer exist in the JQL of a webhook breaks some events on all webhooks in the site

      Issue Summary

      Having a custom field that no longer exist in the JQL of a webhook breaks some events on all webhooks in the site.

      Steps to Reproduce

      1. Create a webhook, including a JQL in it to reduce the scope of it, include a custom field in the JQL. Also, include events like Issue updated in it.
      2. Delete the custom field that is indicated in the JQL of the webhook, from the custom fields catalog.
      3. Perform an action that would trigger the webhook, like updating an issue fields.

      Expected Results

      The webhooks that match the event triggered will send their correspondent web requests for the Issue updated event.

      Actual Results

      All the Issue updated events stop working in all the webhooks in the site regardless if they include the inexistent custom field in their JQL and even if you create a new webhook after the custom field has been deleted.

      Workaround

      Ensure no JQL includes inexistent custom fields in webhooks.

            [JRACLOUD-76472] Having a custom field that no longer exist in the JQL of a webhook breaks some events on all webhooks in the site

            Atlassian Update - November 16, 2023

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - November 16, 2023 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              rchiquete Rene C. [Atlassian Support]
              Affected customers:
              2 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: