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

Allow Confluence anchor links URL tags to work on the knowledge base as well

    • 1
    • 11
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, you can share a Page directly to an anchor link by adding it at the end of the URL, like so:

      • instance.atlassian.net/wiki/spaces/SPACEKEY/pages/page-id#AnchorName

      However, that does not work for the Knowledge Base view, so if you use:

      • instance.atlassian.net/servicedesk/customer/portal/portal-id/article/page-id#AnchorName

      You will be redirected to

      • instance.atlassian.net/servicedesk/customer/AnchorName

      And an error will be shown.

      It'd be beneficial to be able to send Anchor Links on the Knowledge Base just like we can for Confluence.

            [JSDCLOUD-9784] Allow Confluence anchor links URL tags to work on the knowledge base as well

            Giles Middleton added a comment - - edited

            We have the same/similar issue - we moved all our content from zendesk, setup our wikis.

            Then tried to give customers links to content in a wiki, using the little icon to share a link to the articles.

            i.e. "Copy link to heading" which pops up on the right of a heading in an article.

            When the customers follow this link, they are navigated to the top level site, not even the article.

             

            URL from the link icon: https://my.support.myCompany.co.uk/wiki/spaces/MS/pages/123456/articleName#anchor

            Result when followed: https://my.support.myCompany.co.uk/servicedesk/customer/portals

            Link the wiki should have given: https://my.support.myCompany.co.uk/servicedesk/customer/portal/3/article/123456#anchor

             

            Another scenario is when a customer themselves views a help article and wants to discuss it with us, they send us a link and we have to hack the article ID out of the URL to see what it is. 

             

             

            Giles Middleton added a comment - - edited We have the same/similar issue - we moved all our content from zendesk, setup our wikis. Then tried to give customers links to content in a wiki, using the little icon to share a link to the articles. i.e. "Copy link to heading" which pops up on the right of a heading in an article. When the customers follow this link, they are navigated to the top level site, not even the article.   URL from the link icon: https://my.support.myCompany.co.uk/ wiki/spaces/MS/pages/ 123456 / articleName # anchor Result when followed: https://my.support.myCompany.co.uk/servicedesk/customer/ portals Link the wiki should have given: https://my.support.myCompany.co.uk/ servicedesk/customer/portal/3/article/ 123456 # anchor   Another scenario is when a customer themselves views a help article and wants to discuss it with us, they send us a link and we have to hack the article ID out of the URL to see what it is.     

            We'd really like to see some progress on this issue. It has been "gathering interest" for years now, how about "In Progress?

            InfoNgen Help Center added a comment - We'd really like to see some progress on this issue. It has been "gathering interest" for years now, how about "In Progress?

            Mirroring what has already been said. We have a consumer who uses our portal and when they continue to hit walls using links that are provided in the portal, but go to staff Confluence, it's egg-in-the-face for us and negative user experience for them.

            Laurie Egbert added a comment - Mirroring what has already been said. We have a consumer who uses our portal and when they continue to hit walls using links that are provided in the portal, but go to staff Confluence, it's egg-in-the-face for us and negative user experience for them.

            Thomas added a comment -

            We are affected by this too. We have a large KB using lots of anchors and we run into this issue for all links. We need to find a solution for this.

            Thomas added a comment - We are affected by this too. We have a large KB using lots of anchors and we run into this issue for all links. We need to find a solution for this.

            It shouldn't result in an error at all. I understand that the full implementation might take time, but at least a work-around for the error should be in place. It's easy to parse out everything after a hashtag.

             

            Dennis Dolman added a comment - It shouldn't result in an error at all. I understand that the full implementation might take time, but at least a work-around for the error should be in place. It's easy to parse out everything after a hashtag.  

            I can only confirm the comments above. We have longer help pages in our knowledge base and would really need to link to certain parts of the pages specifically. This is especially the case when linking from external sites or apps

            SenseGuard Support (SSO) added a comment - I can only confirm the comments above. We have longer help pages in our knowledge base and would really need to link to certain parts of the pages specifically. This is especially the case when linking from external sites or apps

            We have created a lot of content on our pages, and yhis feature would greatly help in providing customers with the exact location on the Knowledge Base page to find the information they seek.

            Pi Network Support added a comment - We have created a lot of content on our pages, and yhis feature would greatly help in providing customers with the exact location on the Knowledge Base page to find the information they seek.

              Unassigned Unassigned
              asantos2@atlassian.com Augusto Pasqualotto (Inactive)
              Votes:
              50 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: