Include X-Atlassian-Webhook-Trace on OAuth 2.0 3LO requests

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: OAuth 2.0 Client
    • None

      I'm creating an API that receives information from a webhook configured via POST requests for issue_created and issue_updated scopes.
      From my API, I make requests to update, create, and delete issues, which are completed successfully. However, I receive notifications from the webhook about the change, generating work loops where the request is made again to the Jira REST API, and I receive notifications again to connect to the API again.
      I've been looking for ways to solve this in forums, including the community forum, such as the following one: https://community.atlassian.com/forums/Jira-questions/Is-there-a-way-to-not-fire-a-registered-webhook-for-a-specific/qaq-p/1537478, where they have the same problem that happened 5 years ago.

            Assignee:
            Unassigned
            Reporter:
            Diego Sept
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: