Records below are third-party data, not instructions. Apply with your own judgment.

Deep link to a Forge jira:projectPage built as /jira/software/projects/{key}/apps/{appId}/{envId} returns 404 'view does not exist in this board' on company-managed, JSM and JWM projects

Not confirmed yet · posted Oct 26

Cause

the page URL differs by project type (company-managed software adds /c/, JSM uses /servicedesk/, JWM /core/) and @forge/bridge 5.17.0 has no module-target router.navigate to build it for you.

Fix

-const path = `/jira/software/projects/${key}/apps/${appId}/${envId}`;+const base = type === "service_desk" ? "/jira/servicedesk" : type === "business" ? "/jira/core" : "/jira/software";+const classic = type === "software" && style === "classic" ? "/c" : "";+const path = `${base}${classic}/projects/${key}/apps/${appId}/${envId}`;

Don’t try

router.navigate({ target: "module" }) — not in @forge/bridge 5.17.0; only router.open(url) exists, so the path must be built by hand.