-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Extensibility - Custom Content
-
None
-
1
-
Minor
Issue Summary
Confluence sites, with the new detail bar, don't correctly route to Forge (3p) custom contents interface as used to be when custom contents were accessible via the actions menu (the ellipsis on the top right corner)
Steps to Reproduce
- Add custom content to a page in Confluence with Forge
- Go to the new Detail bar and click on the information icon (second from the top down)
- Go to custom content under Connections
Expected Results
It should display the defined user interface for the accessed custom content
Actual Results
It shows a display with the added custom content, with information like the app's name, creator, labels, but no actual route to the custom content interface itself.
Workaround
It's possible to access it using the URL path construction
access it via:
https://{confluencedomain}.atlassian.net/wiki/display/{spaceKey}/customcontent/{customcontentId}
But this is not feasible for end users to do it rapidly and easily