ViewIssueModal (@forge/jira-bridge) — parent breadcrumb is not clickable / no in-modal navigation

Forge Forge Modules and Product Triggers
1

When opening an issue via ViewIssueModal from @forge/jira-bridge, the parent breadcrumb (and linked-issue references) inside the modal are not interactive. The modal is locked to the single issueKey passed in context and cannot navigate to another issue.

In the equivalent Connect API, AP.jira.openIssueDialog(issueKey), the parent breadcrumb is clickable and the dialog re-renders its content in place to show the parent issue — no new dialog/modal is opened. We are migrating a Connect app to Forge and this is a visible regression for users.

Steps to reproduce

  • In a Forge app (e.g. a Jira global page), open a sub-task:

import { ViewIssueModal } from ‘@forge/jira-bridge’;
new ViewIssueModal({ context: { issueKey: ‘ABC-123’ } }).open();

  • In the opened modal, look at the parent issue in the breadcrumb (or any linked issue).

Actual result
The parent breadcrumb is rendered but not clickable; there is no way to navigate to the parent within the modal.

Expected result
Same as Connect AP.jira.openIssueDialog: clicking the parent breadcrumb navigates in place within the same modal to the parent issue.

2

ECO-1268 is closest to what you are after, Add onIssueChange listener for Forge ViewIssueModal class, Gathering Interest with 4 votes. It also carries the only mitigation I found written down anywhere:

Currently, there is no workaround to open a new issue key in the same modal and keep the app open. The closest we have is to use router.open() instead of ViewIssueModal.

So router.open() instead of ViewIssueModal. Links work again and your app closes behind them. Thin, but it is what exists.

JRACLOUD-95802 has more weight at 18 votes. Check its Expected Result before you vote though, it asks for the clicked issue in a new tab, not the in place re-render you had on Connect. Two customers asked for an update there in June and nobody has answered.

Your case may be worth adding to FRGE-2179 instead. That one is filed from a full page app, and it contradicts 95802 on your exact symptom: it reports every link including the parent breadcrumb as navigating the host window, rather than doing nothing.

3

Thanks @Mihai_leanzero for such a wide answer!

I’ve just looked through issues and voted!

Best regards,

Oleh