Frontend routing changes require understanding of workspace/sidebar context.
The issue describes UI inconsistency in the Desk router when navigating between sidebars containing the same DocType. The proposed solution involves modifying the routing structure to include workspace/sidebar context. This requires frontend changes and understanding of the routing system, but the requirements are somewhat clear.
Yes.
The Desk router is confusing when working with multiple workspace sidebars. If a workspace sidebar contains a DocType that is also present in another sidebar, clicking the "View Sidebar" button may redirect to a different sidebar instead of the one the user expects.
This creates ambiguity because the routing is based only on the DocType, not the workspace/sidebar context.
The frontend routing structure should include workspace/sidebar context to avoid ambiguity.
Proposed route structure:
/desk/:workspace_sidebar/:doctype_or_element
Current route structure:
/desk/:doctype
This would ensure:
Claim this issue to let others know you're working on it. You'll earn 20 points when you complete it!