State Mappings Indefinitely Loading for a Jira Space in Jira Align

Summary

When attempting to configure State Mappings for a specific Jira Space in Jira Align (Administration > Jira Settings > Jira Setup > State Mappings), the page displays a continuous spinning wheel and fails to load the mapping interface. This issue may affect only one specific space while others in the same connector work correctly.

Diagnosis

To confirm this is the cause:

1. Generate a HAR file: Capture network logs while attempting to load the failing State Mapping page.

2. Check API Response: Look for a request to /api/jira/statemapping/objecttypeselector.

3. Identify Error: If the response contains a SQL error like "Subquery returned more than 1 value", it confirms a duplicate mapping exists in the backend.

4. Open a support ticket so the team can verify Backend IDs for the Spaces configured in the specific connector on your instance.

Cause

This issue is typically caused by duplicate Jira Space ID mappings within the same Jira Align connector.

When the State Mapping page is requested, the backend executes a query to fetch the relevant project details. If multiple entries in the Jira Align database are associated with the same Jira Project ID for that connector, the SQL query returns multiple values where only one is expected (e.g., Subquery returned more than 1 value), causing the API request to fail and the UI to spin indefinitely.

Solution

To resolve the conflict, you must refresh the project mappings in the Jira Align UI:

1. Navigate to Administration > Jira Settings > Jira Setup.

2. Go to the Manage Projects tab.

3. Locate the affected Jira Space(s) and remove the mapping.

   • Note: If you identified a specific duplicate space during diagnosis, remove both conflicting spaces.

4. Re-add the Jira Space(s) manually through the UI.

5. Navigate back to State Mappings and verify that the page now loads correctly for the affected space.