-
Bug
-
Resolution: Unresolved
-
Medium
-
Minor
Issue Summary
Currently, if you attempt to include a custom field that has a smart link in it (via wiki style rendering), the link ends up being displayed with a pipe, such as:
https://thisismylink.com, or some sort of variation of this. Even if this ends up being clickable (it is not in Office mailboxes), it ends up leading to a 404 as the entire string is hyperlinked.
Steps to Reproduce
- Create custom field with wikistyle rendering.
- Create automation to email someone including the smart value for that custom field in it.
- View email, see that smart linking has broken the URL included.
Expected Results
URL should display as a simple link, either full URL text or shortened, and should be working.
Actual Results
URL displays as broken due to entire raw smart link being used in the email, regardless of whether it's clickable or not.
Note that there was an attempt to semi address this (by disabling it completely) via this feature request: JRACLOUD-72429
However, that feature request was closed and smart linking is forced as you can't disable it all, making all emails that have URLs involving smart links useless.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- causes
-
JSDCLOUD-12746 When inserting a link into a jira description using the rich text link option, whenever the description field is sent out via email from an Automation rule, the formatting breaks.
-
- Closed
-
- is duplicated by
-
AUTO-286 Automation: URL from smart values not rendered as expected in emails
- Closed