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

Service Desk automation action to send webhooks should be able to include system and custom fields in the payload

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Automation
    • Labels:
      None
    • UIS:
      1
    • Feedback Policy:
      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.

      Description

      Problem Definition

      When using the Jira Service Desk automation it is possible to setup an action of sending a webhook. However the available fields in which you can choose to add as part of the webhook payload is very limited to a predefined list. Currently as of 4.11, you can only choose the following fields:

      • Recipient Name
      • Portal name
      • Name of person who caused the action
      • Issue summary
      • Issue description
      • Issue key
      • Issue reporter
      • Issue resolution
      • Request URL
      • Request status
      • Request details.

      Suggested Solution

      Allow for all issue fields (both system fields and custom fields) to be included in the json payload of that automation webhook.

      Why this is important

      This is already possible in Jira Cloud, due to the integration of codebarrel automation across all projects. This is important because the current state greatly limits the ability to integrate JSD server with other 3rd party products.

      Workaround

      The Automation for Jira Server plugin (Full version, not Lite) is able to do send webhooks as an automation action.  Also you can use Smart values in that automation rule in order to select any field in the issue to be included as part of the json payload.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            aheinzer Andy Heinzer
            Votes:
            4 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but there is no synchronization info for this issue.