Unable to insert a shortcut link in confluence cloud

[Tim de Boer]

I am unable to use shotcut links in confluence cloud. The documentation says I should be able to use [relativeurl@shortcut]. I have shotcuts configured as per the first image and am trying to edit as per the second image but the result I get is the third image 

_____________________________________________________________

_________________________________________________________________

I have also tried to use the /link macro and can't seem to find a combination there that is documented and/or works.

Thanks

Tim

[Brant Schroeder · Accepted solution]

@Tim de Boer  Welcome to the Atlassian Community.

Is that url valid?  When I tried to reach it nothing was there and I got page not found.  Can you check the url and make sure you are reaching a valid page.

[Tim de Boer]

Hi Brant. The full url is https://www.commerce.wa.gov.au/sites/default/files/atoms/files/gslr_circular_5_2021.pdf

[Brant Schroeder]

@Tim de Boer Thanks for providing the url, I tested it out and found the issue.  Shortcut links only work in the legacy editor.  https://support.atlassian.com/confluence-cloud/docs/configure-shortcut-links/

I believe you can request to be moved back to the legacy editor by submitting a support request to Atlassian.

[Tim de Boer]

Thanks for trying Brant. 

We're providing this site as a service to one of our clients. Defaulting them to the legacy editor doesn't feel ike the right option and from memory that won't default them to the legacy editor in every case. Only when templates etc specify. 

I don't expect an answer to this but just want to drive home how important the editing experience in confluence is. It's one of the reasons we decided to be an Atlassian partner.

I do feel like this important element is receiving far less attention strategically than it should. Your community is filled with people suffering from basic limitations to the editing experience (such as the inability to indent within layouts, tables etc and the unusual decision to limit the colour pallette) which Atlassian refuses to fix. The severity of the limitations can't be denied so the only reason I can see for this decision is that their attention is elsewhere. 

Let's just hope Atlassian decides to spend a little more attention and money in this area soon!

Thanks

Tim