Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8663

Adding issue link into a description field with the service desk automation rule breaks a hyperlink

      Issue Summary

      Inserting an issue key into a description field with the service desk automation rule will create an invisible character in the issue key so that it will break a hyperlink.

      Steps to Reproduce

      1. Create an automation rule to create an issue on some action(example: comment added).
      2. Configure the description to create issue link using the variable ${sourceissue.key}Description looks like this:

                Service Desk Ticket ID:
               https://test.atlassian.net/servicedesk/customer/portal/1/$

      {sourceissue.key}
      1. Add comment to the issue Test-1

      Expected Results

       Should create an issue with description and link should navigate to issue

                 Service Desk Ticket ID:
                https://test.atlassian.net/servicedesk/customer/portal/1/Test-1 

      Actual Results

      Creates an issue with description and link is broken

                 Service Desk Ticket ID:
                https://test.atlassian.net/servicedesk/customer/portal/1/Test<200c>-1

       

      Workaround

      Copy the url and remove the '<200c>'

            [JSDCLOUD-8663] Adding issue link into a description field with the service desk automation rule breaks a hyperlink

            Nicole added a comment -
            Atlassian Update - December 1, 2020

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com.

            Thank you again for providing valuable feedback to our team!
            Jira Service Management Cloud team

            Nicole added a comment - Atlassian Update - December 1, 2020 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com . Thank you again for providing valuable feedback to our team! Jira Service Management Cloud team

              Unassigned Unassigned
              apradhan2 Abhishek
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: