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

Webresponse.body.url smartvalue includes an extra slash in the href when the link is autogenerated

XMLWordPrintable

    • Minor
    • Jira Software, Jira Service Management, Jira Work Management

      Issue Summary

      Webresponse.body.url smart value includes an extra slash in the href when the link is autogenerated, which can lead to issues. 

       

      Example URL: https://www.atlassian.com

      Generated link: https://www.atlassian.com/

      Steps to Reproduce

      1. Create an automation rule that uses a Send Web Request action to gather data from an external system. The response should include an url in the body.
      2. Use the webResponse.body.url smart value to add a comment in the issue with the Comment on issue action.
      3. Evidence that the added comment includes an autogenerated link, which href includes an extra slash.

      Expected Results

      The generated HREF should point to the same URL without the extra slash

      Actual Results

      The HREF includes an extra slash

      Workaround

      Using the markup syntax to add the link is a viable workaround. Instead of:

      {{webResponse.body.url}}

      Please use

      [{{webResponse.body.url}}]

      or

      [link name|{{webResponse.body.url}}]

        1. image-2024-07-15-11-55-01-435.png
          261 kB
          Alejandro Scuncia
        2. image-2024-07-15-11-55-44-983.png
          256 kB
          Alejandro Scuncia

            [AUTO-1364] Webresponse.body.url smartvalue includes an extra slash in the href when the link is autogenerated

            Maggie So added a comment - - edited

            Cannot reproduce this bug using a rule configuration with the following structure:

            1. Scheduled trigger on an issue
            2. Send web request action with GET method
            3. Access response body using smart values and access a field with a URL in it and put it into the Log action
            4. Access response body using smart values and access a field with a URL in it and put it into a Comment on Issue action

            When running the rule, verified that the URL in the response body has no extra slash at the end of it by directly accessing the endpoint. Verified that the Log action returns that same exact URL without the extra slash, meaning automation didnt do anything to the URL to add a slash. Verified that the comment on issue action returns that same exact URL without the extra slash, meaning Jira didnt do anything extra to the URL to add a slash.

            Attempted to reproduce this bug using three different endpoints, two using GET and one using a POST method

            Maggie So added a comment - - edited Cannot reproduce this bug using a rule configuration with the following structure: Scheduled trigger on an issue Send web request action with GET method Access response body using smart values and access a field with a URL in it and put it into the Log action Access response body using smart values and access a field with a URL in it and put it into a Comment on Issue action When running the rule, verified that the URL in the response body has no extra slash at the end of it by directly accessing the endpoint. Verified that the Log action returns that same exact URL without the extra slash, meaning automation didnt do anything to the URL to add a slash. Verified that the comment on issue action returns that same exact URL without the extra slash, meaning Jira didnt do anything extra to the URL to add a slash. Attempted to reproduce this bug using three different endpoints, two using GET and one using a POST method

              Unassigned Unassigned
              91ab64c19c3b Alejandro Scuncia (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: