---
title: "Issue Matrix Forge Panel Not Appearing After Migration"
canonical: "https://support.appfire.com/space/SUPPORT/3426746388/Issue%20Matrix%20Forge%20Panel%20Not%20Appearing%20After%20Migration"
format: markdown
---
### Summary
This article covers two distinct scenarios related to the Issue Matrix Forge panel visibility in Jira Cloud following a migration from Data Center (DC).
Before diving into those two scenarios, review the following information about what you'll need to do after a Forge upgrade.
> đ Issue Matrix for Jira Cloud has moved to the [Forge - Runs on Atlassian (RoA)](https://developer.atlassian.com/platform/forge/runs-on-atlassian/) framework.
> đ
> đ **Connect end of support**:
> đ
> đ - Atlassian has [announced](https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps) the end of support for the Connect framework in late 2026.
> đ - Appfire recommends upgrading the Issue Matrix for Jira Cloud to the Forge-RoA version to stay current with future enhancements and security updates.
**After a Forge upgrade**
1. Open a work item and click the **View app actions** button. You'll see the **Issue Matrix for Jira** option; click it. This enables the matrix for this work item.
2. You'll also need to click the **Actions** (...) button on the matrix and select the **Show for all work items** option. This enables the matrix for all work items in this project.
> âšī¸ You'll need to do steps 1 and 2 for all projects, since the **Show for all work items** option is enabled on a per-project basis.
![NEWShowForAllWorkItems.png]()
### Scenario 1: missing Forge panel due to migration errors
The Issue Matrix panel doesn't appear in the "View app actions" menu for specific projects, despite a successful JCMA report.
**Screenshot:**
**Problem**
After a JCMA migration, the Issue Matrix Forge panel is missing from the "View app actions" menu in certain projects, even though:
- The JCMA migration log reports 100% success.
- The `atlassian-addons-project-access` role is correctly assigned.
- Matrix configurations are visible and enabled in **Project Settings**.
**Cause**
A **403 error** during the initial migration can prevent Forge storage from properly persisting Issue Matrix configurations for specific projects. This is particularly common in projects linked via multi-project matrices, where the panel registration might not trigger correctly.
**Solution**
Appfire released a patch on June 25, 2026 to address this. To resolve the issue, re-migrate the app data for the affected projects.
### Scenario 2: inconsistent panel visibility due to permissions
The Forge panel requires specific user permissions to be enabled and rendered, which leads to inconsistent access across different projects.
**Problem**
A user can see and enable the Issue Matrix panel in some projects but not others. The "Add apps" option is visible, but the Issue Matrix option is missing from the menu.
**Screenshot:**
**Cause**
This is due to a **Jira Cloud platform limitation** for the `jira:issuePanel` module (tracked by Atlassian as ACJIRA-2111 / ECO-421). Unlike DC, where **Browse Projects** permission was sufficient, the Forge issue panel in Cloud requires specific permissions for the initial enablement.
**Permission requirements**
- **To view an already-enabled panel:** **Browse Projects** permission (plus a valid app license).
- **To add or enable the panel via the "Apps" menu:** **Edit Issues** permission.
**Solution/workaround**
If a user can't see the option to add the panel, it's likely due to missing **Edit Issues** permissions in that specific project.
1. **Service account workaround:** Use a service account or an administrator account with **Edit Issues** permission to enable the panel once per project (using the "Show for all work items" setting).
2. **Grant permissions:** Temporarily or permanently grant **Edit Issues** permission to the users who need to enable the panel.
3. **Admin enablement:** Have a project admin enable the panel. Once it's enabled, all other users with **Browse Projects** permission will be able to view it.
**Related information**
- **Bulk enablement:** There's currently no REST API or automation method to bulk-enable Issue Matrix panels across all projects. You'll need to do this per project through the UI.
- **Forge architecture:** This behavior results from the Forge "opt-in" issue panel design, and Appfire classifies it as a platform behavioral difference rather than an app bug.