This is reproducible on Data Center: (yes) / (no)
- Create a simple Connect app that opens a Jira issue (containing child/linked issues) using Connect JS API: AP.jira.openIssueDialog (e.g. by clicking a button which calls the API to launch the dialog)
- Install the Connect app in a test Jira site (see Getting started with Connect for more info)
- Trigger the API to be called to open an issue dialog (e.g. by clicking the button you have created)
- Click a child/linked issue and observe the new contents within the modal.
The clicked issue opens within the Bento modal, loading all its data correctly, replacing the current issue. Or it opens full-page but then please target=”_blank”. Don’t replace the current (Connect app’s) page.
The clicked issue opens within the Bento modal, however replaces only some fields. As a result, there is information about the previous viewed issue and and the clicked issue within the same modal.
The page is also navigated away from the Connect app’s page, losing it’s context.
Currently there is no known workaround for this behavior. A workaround will be added here when available