Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5538

JSON payload of automation webhook should tell internal from public comment

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 0
    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Summary

      Using an automation to send a webhook for comment added event, the JSON payload of the webhook doesn't contain information on comment type, so it's not possible to tell whether the added comment is internal or public. This makes it hard to process the JSON data.

      Suggestion

      Include comment type in JSON payload for automation webhook.

            [JSDSERVER-5538] JSON payload of automation webhook should tell internal from public comment

            Charlie Marriott added a comment -
            Atlassian Update – 5 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 5 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Charlie Jira Service Management, Server & Data Center

            Nathan Neulinger added a comment -

            Patch attached to JRASERVER-59980 seems to return a bunch of data into the web hook as a side effect - it's possible that it would resolve this issue as well, but haven't specifically looked. It's at least a starting point.

            Nathan Neulinger added a comment - Patch attached to JRASERVER-59980 seems to return a bunch of data into the web hook as a side effect - it's possible that it would resolve this issue as well, but haven't specifically looked. It's at least a starting point.

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: