• 0
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Atlassian status as of August 2019

      Shortcut links were introduced in Confluence 2.3 and provided a quick way to add links to websites in wiki markup. Shortcut links can only be configured by an administrator, are not easily discoverable, and seldom used by end users.

      We had planned to end support for Shortcut Links in Confluence 7.0, but we've heard your feedback, and will not end support at this time.

      Feel free to comment on this issue if this change will have a significant impact on your Confluence site.

      Find out more about our other planned changes in Confluence 7.0

          Form Name

            [CONFSERVER-57610] Plans to end support for shortcut links

            It still says "We ended support for shortcut links in Confluence 7.0
            Shortcut links can still be added and used on pages, but we will no longer fix bugs relating to this feature, and plan to remove it in a future Confluence release."

            Jan-Ove Nesheim added a comment - It still says " We  ended support  for shortcut links in Confluence 7.0 Shortcut links can still be added and used on pages, but we will no longer fix bugs relating to this feature, and plan to remove it in a future Confluence release."

            Apologies for the confusion, I missed that page when updating the 7.0 docs. I've updated it now. Shortcut links are still supported for the foreseeable future.

            Rachel Robins added a comment - Apologies for the confusion, I missed that page when updating the 7.0 docs. I've updated it now. Shortcut links are still supported for the foreseeable future.

            According to documentation https://confluence.atlassian.com/doc/configuring-shortcut-links-135903.html you do end support in Confluence 7 - which is true?

            Jan-Ove Nesheim added a comment - According to documentation  https://confluence.atlassian.com/doc/configuring-shortcut-links-135903.html  you do end support in Confluence 7 - which is true?

            Thank you!

            Scott Cantor added a comment - Thank you!

            Thanks for hearing us – good news!

            Normand Brousseau added a comment - Thanks for hearing us – good news!

            Thanks for your feedback on this issue. We've heard you, and will make no changes to Shortcut Links in Confluence 7.0.

            Emily Chan (Inactive) added a comment - Thanks for your feedback on this issue. We've heard you, and will make no changes to Shortcut Links in Confluence 7.0.

            Emily Chan (Inactive) added a comment - - edited

            Thank you afuerth alexandros.emmanouil norbro cantor.2@osu.edu mlad for providing your feedback!

            We would like to further understand the use cases of this feature, and the impact of ending support for this feature. To do so, we would really appreciate if you, or any other customer who strongly rely on this feature, could chat with us for about 30-40 mins. 

            Please email me at echan@atlassian.com to arrange a chat. 

            ------------

            norbro For this issue (and similarly for all other issues with the 7.0-deprecations label attached), “Vote for this issue” would mean “Yes, end support for shortcut links”.

            We’re aware that there’s been some customers who voted for these issues, when they are actually against the end-of-support. Thankfully, they had provided their comments on those issues which clearly stated their stance.

             

            Emily Chan (Inactive) added a comment - - edited Thank you afuerth alexandros.emmanouil norbro cantor.2@osu.edu mlad for providing your feedback! We would like to further understand the use cases of this feature, and the impact of ending support for this feature. To do so, we would really appreciate if you, or any other customer who strongly rely on this feature, could chat with us for about 30-40 mins.  Please email me at  echan@atlassian.com  to arrange a chat.  ------------ norbro  For this issue (and similarly for all other issues with the 7.0-deprecations label attached), “Vote for this issue” would mean “Yes, end support for shortcut links”. We’re aware that there’s been some customers who voted for these issues, when they are actually against the end-of-support. Thankfully, they had provided their comments on those issues which clearly stated their stance.  

            We extensively use shortcut links in order to make hidden features available to users in our PRODuction instance, and to make it possible for them to try out the same links in our TEST environment.

            One example: we use the '@doc' shortcut to set the value for the 'Dark features' user parameter page to 'users/darkfeatures.action@doc', which is translated in our PRODuction instance as: https://OUR-*PRODUCTION*-BASE-URL/users/darkfeatures.action.

            When "refreshing" our TEST instance, we restore the PRODuction mySql dump to the test server, and the Restore script edits the shortcut link '@doc', which is one single entry in the BANDANA table. Then the same shortcut link is now translated as '
            https://OUR-*TEST*-BASE-URL/users/darkfeatures.action, and there is no risk for users to edit their PRODuction parameters while they only intended to try them out in the TEST instance.

            Very useful!
            ---------------
            Also one question to Atlassian people: What does 'Vote for this issue' mean, in the context of this specific page? 'YES, end support for shorcut links', or else 'YES, please keep shorcut links'???

            Normand Brousseau added a comment - We extensively use shortcut links in order to make hidden features available to users in our PRODuction instance, and to make it possible for them to try out the same links in our TEST environment. One example: we use the '@doc' shortcut to set the value for the 'Dark features' user parameter page to 'users/darkfeatures.action@doc', which is translated in our PRODuction instance as: https://OUR-*PRODUCTION*-BASE-URL/users/darkfeatures.action . When "refreshing" our TEST instance, we restore the PRODuction mySql dump to the test server, and the Restore script edits the shortcut link '@doc', which is one single entry in the BANDANA table. Then the same shortcut link is now translated as ' https://OUR-*TEST*-BASE-URL/users/darkfeatures.action , and there is no risk for users to edit their PRODuction parameters while they only intended to try them out in the TEST instance. Very useful! --------------- Also one question to Atlassian people: What does 'Vote for this issue' mean, in the context of this specific page? 'YES, end support for shorcut links', or else 'YES, please keep shorcut links'???

            I agree with previews people.

            We use heavy this feature. Shortlinks provides a powerful method to manage linking to other websites in our company like a service desk, intranet sites, local systems.

            We have many tutorials about how to use preconfigured shorcut links.

             

            Maciej Ląd added a comment - I agree with previews people. We use heavy this feature. Shortlinks provides a powerful method to manage linking to other websites in our company like a service desk, intranet sites, local systems. We have many tutorials about how to use preconfigured shorcut links.  

            My vote also, they're extremely useful for managing links to Javadocs and other kinds of scenarios where the details of the target system are complex. Not all wikis are extensively edited by "end users". Please do not remove this feaure, it can't be that hard to leave around. If you do remove it, then please provide a clean migration that doesn't break them all. I assume that at least is a given.

            Scott Cantor added a comment - My vote also, they're extremely useful for managing links to Javadocs and other kinds of scenarios where the details of the target system are complex. Not all wikis are extensively edited by "end users". Please do not remove this feaure, it can't be that hard to leave around. If you do remove it, then please provide a clean migration that doesn't break them all. I assume that at least is a given.

              Unassigned Unassigned
              rrobins Rachel Robins
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: