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

JIRA Service Desk "Then Webhook" could not validate some character

XMLWordPrintable

    • 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.

      Steps to Reproduce:

      1. Navigate to a JIRA Service Desk Project
      2. Move to the Project Administartion page and click "Automation".
      3. Create a Custom Rule and set any "IF" condition
      4. Choose Webhook for the "Then" condition.
      5. Put a Random URL like: 
        http://localhost:8080/jira/{}
      6. Click Confirm

      Expected Result:

      • The URL will be accepted

      Actualy Result:

      • "Invalid URL provided" error message will be shown.

      Notes:

      • Tried with ?,$,& it work so far
      • Using JIRA standard Webhook is accepted as well.

            [JSDSERVER-4435] JIRA Service Desk "Then Webhook" could not validate some character

            Charlie Marriott added a comment -
            Atlassian Update – 11 Jan 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,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 11 Jan 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, Jira Service Management, Server & Data Center

            Thomas David Trueman added a comment -

            Is there any news on this issue?

            We are looking to hookup Jira to teams to give us updates when a ticket is updated, but if this is not working then it's not possible?

            If anyone knows of another solution please sling it my way  

            Thomas David Trueman added a comment - Is there any news on this issue? We are looking to hookup Jira to teams to give us updates when a ticket is updated, but if this is not working then it's not possible? If anyone knows of another solution please sling it my way  

            Tim Eddelbüttel added a comment -

            It's unbelievable to me that this is still not fixed / implemented (depending on the personal opinion what it is).

            JSD automation rules are still are really limited without variables like ${issue.key} in the Webhook URL. That makes also ScriptRunner REST Endpoints hard to use.

            Tim Eddelbüttel added a comment - It's unbelievable to me that this is still not fixed / implemented (depending on the personal opinion what it is). JSD automation rules are still are really limited without variables like ${issue.key} in the Webhook URL. That makes also ScriptRunner REST Endpoints hard to use.

            Tim Eddelbüttel added a comment -

            Any progress on this? Without usable variables in SD Automation Webhook it's useless.

            On the other hand, webhooks from JIRA Core can't be used, because the can't do any kind of authentication.

            JRA-31953

            Tim Eddelbüttel added a comment - Any progress on this? Without usable variables in SD Automation Webhook it's useless. On the other hand, webhooks from JIRA Core can't be used, because the can't do any kind of authentication. JRA-31953

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: