---
title: "Delegated Project Creator for Jira: Troubleshooting blank migration Pages"
canonical: "https://support.appfire.com/space/SUPPORT/3064922196/Delegated%20Project%20Creator%20for%20Jira%3A%20Troubleshooting%20blank%20migration%20Pages"
format: markdown
---
## **Issue:**

After migrating the Delegated Project Creator for Jira (DPC) app from Data Center to Cloud, users may encounter an issue where all administrative sections, such as **General Configuration**, **Project Templates**, **Project Request Settings**, and **Audit Logs, **appear blank.

This article outlines the most common causes and step-by-step troubleshooting actions to resolve the issue.

---

## **Symptoms**

- All DPC configuration pages are blank:
  - **General Configuration**
  - **Project Request Settings**
  - **Project Template Settings**
  - **Audit Logs and Reports**
- Issue persists across:
  - Multipe browsers
  - Incognito and private sessions
  - After app reinstallation
- No UI elements (tables, buttons, or empty-state messages) are displayed.

---

## **Possible Causes**

### **1. Network or firewall restrictions**

The app relies on external services. If these are blocked at the network level, UI components may fail to load, resulting in blank pages.

---

### **2. Missing Atlassian system group**

The atlassian-addons-admin group is required for Atlassian Connect apps to function properly. If this group is missing or lacks permissions, the app may fail to load data.

---

### **3. Incomplete migration or configuration**

Post migration, especially sandbox or partial migrations:

- App configurations (templates, permissions) may not be migrated.
- The app may not be properly initialized.

---

### **4. Permission issues**

Insufficient global or app-level permissions can prevent the UI from rendering correctly.

---

### **5. Browser or cache issues (less likely)**

Although less common, browser extensions or cached data may interfere with app rendering.

---

## **Troubleshooting steps**

### **Step 1: Verify network and firewall settings**

Ensure that the following domains are allowed:

```
pcfj.wittified.appfire.app  
common.appfire.app
```

- Coordinate with your network and security teams and confirm that these domains are not blocked.
- After allowing the list, reload the application pages.

---

### **Step 2: Check Atlassian system group**

1. Navigate to:
2. Verify:
  - The atlassian-addons-admin group exists.
  - It has the **Administer Jira** permission.

**Important:**

If the group is missing, it cannot be manually created. Contact Atlassian Support to restore it.

---

### **Step 3: Validate user permissions**

Ensure that:

- Your user account has **Jira Administrator** access.
- You have permissions to create and manage projects.

---

### **Step 4: Reinitialize the application**

1. Go to: Jira Settings > System > Global Permissions
2. Locate **Delegated Project Creator**
3. Perform:
  - Uninstall the app.
  - Reinstall it from Atlassian Marketplace.
4. After reinstall:
  - Attempt to create a new project template.
  - Verify if the UI sections load correctly.

---

### **Step 5: Perform browser-level checks**

- Open the app in **Incognito or Private mode**.
- Disable browser extensions.
- Test in an alternate browser.

---

### **Step 6: Capture logs for analysis**

If the issue persists:

1. Open Developer Tools (F12).
2. Check the:
  - **Console tab** for errors.
  - **Network tab** for failed requests (e.g., 403, 404, 500).
3. Export a **HAR file** and share it with Appfire support.

---

### **Step 7: Confirm app version**

Ensure the latest version of the app is installed:

```
Jira Settings > Apps > Manage Apps
```