Router.open({ target: "module" }) navigates to /not-found for team-managed business projects

Forge Forge UI Kit and Custom UI
1

I’m using @forge/bridge router.open with target:“module” to navigate to a jira:projectPage.

Manifest:

modules:
jira:projectPage:
- key: jira-project

Code:

await router.open({
target: “module”,
moduleKey: “jira-project”,
projectKey: “TT3”
});

Expected:
For team-managed business project TT3, Jira should open:
https://.atlassian.net/jira/core/projects/TT3/apps/{appId}/{envId}

Actual:
router.open first resolves to:
https://.atlassian.net/jira/software/projects/TT3/apps/{appId}/{envId}

Jira then redirects automatically to:
https://.atlassian.net/jira/core/projects/TT3/not-found

Notes:

  • Works correctly for software projects
  • Fails only for team-managed business projects
  • Direct navigation to the correct /jira/core/…/apps/… URL works
  • router.open NavigationLocation is Preview

Question:
Is this a known limitation/bug in NavigationLocation resolution for team-managed business projects?
Is URL-based navigation the recommended workaround?

Forge version:
@forge/bridge ^5.10.1

1 Like