Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-896

Issue field text with formatting markdown, @mentions, attachments, etc. is rendered as that raw text in Opsgenie when using Jira/JSM Cloud integrations

XMLWordPrintable

      Issue Summary

      When creating issues or adding comments to issues in Jira, the resulting data sent to Opsgenie is sent in raw text format, with all of the underlying markdown rendered as text as well. So, for example - an @ mention would show up as accountid:5cbfaecfasfdasdfb********* in the alert data and in the alert field. Similar behavior for images/attachments and other formatting elements. 

      Steps to Reproduce

      1. With a Jira/JSM cloud integration - create an issue in Jira with @ mentions, text formatting, images, etc. in the description - you will see the result of that in the alert's description. This is also reproducible with comments >> notes

      Expected Results

      While there's no expectation that Opsgenie will respect markdown formatting, it would be preferable to show just the text itself (and, importantly, the user/entity name instead of id with @ mentions)

      Actual Results

      See above - all formatting/etc. is rendered as plain text

      Workaround

      N/A

            [OPSGENIE-896] Issue field text with formatting markdown, @mentions, attachments, etc. is rendered as that raw text in Opsgenie when using Jira/JSM Cloud integrations

            Mikel Stous added a comment -

            Also, the inverse.  We're having trouble with HTML tags from OpsGenie -> JSM.   Would be good to have a setting to strip out HTML and Markdown tags going from one product to another, until a html/markdown conversion is available.

             

            Mikel Stous added a comment - Also, the inverse.  We're having trouble with HTML tags from OpsGenie -> JSM.   Would be good to have a setting to strip out HTML and Markdown tags going from one product to another, until a html/markdown conversion is available.  

              Unassigned Unassigned
              jsitarz@atlassian.com Justin Sitarz
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated: