Support resolving internal article links within the Document360 portal
backlog
V
Vijay Sakthivel
Currently, when internal article links (relative URLs) are clicked from within the Document360 portal, the system redirects the user to the project dashboard instead of navigating to the corresponding article.
This occurs because the portal uses a different routing structure that expects specific identifiers such as the project ID, category ID, and article ID in the URL. As a result, relative article URLs cannot be resolved correctly within the portal environment.
However, the same relative URLs work as expected when accessed from the Knowledge Base site, where they successfully navigate to the intended article.
For documentation teams who frequently work within the Document360 portal to review content, validate internal links, and test navigation between articles, it would be helpful if internal article links could resolve correctly within the portal as well.
Log In
Z
Zinc Anteater
Makes a lot of sense. You have my vote. Thank you.
Mohamed Shakheen
marked this post as
backlog
Mohamed Shakheen
Hi Educational Quail
Thank you for clearly outlining the behavior and use case.
While relative URLs function as expected on the Knowledge Base site, the portal operates on a different routing structure that depends on specific identifiers (project, category, and article IDs). Due to this, relative links are currently not resolved correctly within the portal.
We recognize that this creates friction for documentation teams, particularly during content validation, internal link verification, and review workflows carried out within the portal.
This has been captured as an enhancement request to improve internal link resolution in the portal environment. Supporting seamless navigation for relative URLs would meaningfully improve the authoring and QA experience.
We will evaluate this as part of our roadmap, with prioritization driven by customer demand and overall impact.
V
Vijay Sakthivel
Raised on behalf of Educational Quail