EDIT (2026-08-18): New finding since posting. The behaviour tracks the Jira plan tier, not time. On our two Free sites the panel is always expanded; on our Standard site it is always collapsed. Identical app code on all three, and none of them preserve the state when you toggle and reopen. That is the defect, and everything below still reproduces.
Our Forge app’s `jira:issueContext` panel has stopped persisting its per-user expand/collapse state. It returns to collapsed on every issue view.
**Expected**
Per the [Issue Context docs](https://developer.atlassian.com/cloud/jira/platform/modules/issue-context/): “the panel also remembers whether a user expanded or collapsed it last time. If a user expands the panel before they exit the issue, it’ll be expanded again when they revisit it.” The [issue view design guidelines](https://developer.atlassian.com/cloud/jira/platform/issue-view/) add that the state is remembered for every issue in the project.
**Actual**
The remembered state is never applied. The panel is collapsed on every issue.
**Environment**
Forge app, `jira:issueContext` with `render: native` (UI Kit, `@forgeforge/react` 11.x, `@forge/bridge` 5.x, nodejs22.x). Jira Software Cloud, new issue view, company-managed project. Single user, single project, no reinstall or redeploy between steps.
**Steps to reproduce**
1. Open an issue from the board (detail modal). Panel is collapsed.
2. Expand the panel. Close the modal.
3. Reopen the same issue. Panel is collapsed again.
4. Repeat with a full page load: open the issue in a new tab. Collapsed.
5. Expand it. Return to the board, open the same issue in a new tab. Collapsed.
Reproduces in both the board detail modal and the full-page issue view, so it is not modal-specific.
**Control 1: native sections persist correctly**
In the same session, same project, same user, expanding “Development” and “More fields” on one story and then opening a different story restores both as expanded. That preference is shared and applied consistently across both the board detail modal and the full-page issue view. Our `jira:issueContext` panel renders in the same issue view alongside those sections and does not participate in that persistence.
**Control 2: not caused by conditional display**
The module normally uses `displayConditions.jiraExpression` to hide the panel on projects where the app is disabled. Removing `displayConditions` entirely and redeploying produces identical behavior. We confirmed the modified build was live by observing the panel entry render on a project where the app is disabled, which is only possible with the condition removed. Conditional display is not a factor.
**Timing**
This worked previously on our site. We do not have a precise date for when it stopped, but the current behavior is consistent and reproducible.
**Related**
Related but distinct: JRACLOUD-98215 covers native sections only and does not address app panels.
**Ask**
Can others confirm whether their `jira:issueContext` panels still persist expand/collapse state? We are on UI Kit (`render: native`), but nothing here appears UI Kit specific, so confirmation from Custom UI context panels would be useful too. Trying to establish whether this is site-specific or a platform-wide regression.
Thanks in advance for any confirmations.