Hey - Had a reply from Workfront which was basically, alot of people wanted to have the URLs shortened for 'Aesthetics' I hoped they would realise functionality over aesthetics on URL's is more important - if the URL is too long then use bit.ly:
"Thank you for reaching out to Workfront support! This is currently working as designed, a significant customer complaint before the 2018.2 (18.2) release was that long URLs caused issues when wrapping to multiple lines and looked unprofessional in the update stream. With industry URLs continually getting longer, Workfront addressed this problem by having the code recognize URL addresses and shorten them where possible as well as creating ellipses when the URL is very long. The complete URL is stored, and when the URL is clicked users are taken to the intended webpage. Workfront also understands that there are cases where customers need the complete URL including the HTTP, or HTTPS as well as the WWW at the beginning of the URL. In those cases, we suggest using the Hyperlink option at the bottom of the Update area (chain link icon). Posting the URL here will allow the complete text to show in the Update. "
^^ The above is not helpful when we're pasting URL strings and scripts into the updates section, for another team to then work with developers using these scripts - in HTML and CSS/Less you need the full URL or the code simply won't work - when your embedding content onto a partners website referencing for an iframe housed on our website you need the
https://www It's not about the user reading the comments simply clicking the URL, it's about the physical alphanumerical characters being used in the embed code and they need to be exactly as written, not shortened by Workfront. To have to copy the code into the updates, then highlight the URL string, click the 'link' button and then paste the URL in to make sure the full URL is held.....is not lean or efficient within my team/business. Scott Smith Head of Production UNiDAYS
