Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-954

Prevent or restrict the possibility to change the automation rule Incoming Webhook endpoint

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Trigger - Other
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Jira Software, Jira Service Management, Jira Work Management

      Issue Summary

      When exporting an automation rule with an Incoming Webhook, the JSON data can be updated to change the Webhook Tag into any text value. Once imported, it is working as desired.

      If the imported automation rule has an existing Webhook Tag that resides on another Jira Cloud instance, the newly imported rule is automatically disabled with an error message “The incoming webhook URL is already in use by another trigger. Please regenerate!“.

      Steps to Reproduce

      1. Create a rule with an “Incoming Webhook” trigger.
      2. Export it to JSON.
      3. Edit the generated webhook token to a custom one, e.g. https://automation.atlassian.com/pro/hooks/TEST.
      4. Import the rule again.
      5. Post a request to https://automation.atlassian.com/pro/hooks/TEST, and the rule will be executed.

      Expected Results

      The webhook tag should not be able to be changed to any text pattern/string.

      Actual Results

      The webhook tag can be changed into any free text.

      Workaround

      N/A

            [AUTO-954] Prevent or restrict the possibility to change the automation rule Incoming Webhook endpoint

            There are no comments yet on this issue.

              Unassigned Unassigned
              c2812f12fd8c Adam Wood (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: