Issue Summary

When using a webhook to get issue updates or creation the Description field is escaping characters such as '[' with multiple escapes and being returned as

\\[

This results in problems with API integrations where users get the value from webhooks to update issues.

The problem is more explicitly using API v3 with the ADF format as when the description is updated with the escape character from the webhook it will also add more escape characters, for example:

• Issue description is set to "test [.]"
• Webhook sends it using two escapes

  test \\[.]
  

• The value is used as-is to update a description using ADF

  {
    "version": 1,
    "type": "doc",
    "content": [
      {
        "type": "paragraph",
        "content": [
          {
            "type": "text",
            "text": "test \\[.]"
          }
        ]
      }
    ]
  }
  

• The description of the issue is displayed as 

  test \[.] 

• The webhook then returns the description as "test \\\\\\[.]" using multiple escapes on both the '\' and the '[' characters

Steps to Reproduce

1. Create a Webhook to fire upon issue creation/update
2. Open an issue and edit its description with the example text test [.]

Expected Results

The JSON response from the webhook should have returned the description text as displayed in the issue test [.]

Actual Results

The JSON response sent is adding two escape characters returning

test \\[.]

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available