Issue Accessing Project Gantt Chart from the Project Menu

Incident Summary

On May 12, 2026, after the release of WBS Gantt-Chart for Jira version 3.0.0, some customers experienced an issue where the Gantt chart failed to fully load when accessed from the project page menu (current space page menu). This issue only affected customers who manually updated to version 3.x.x.

The issue did not occur when users accessed the Gantt chart from the Jira sidebar Apps menu and opened the chart from the Gantt chart list page.

The incident was caused by changes related to the migration from Connect modules to Forge modules. Specifically, the implementation did not sufficiently account for the large volume of data present in the production database environment. As a result, behavior that worked correctly in development, verification, and staging environments failed under production-scale data conditions.

The issue was identified shortly after release, and a fix was deployed on the same day. The incident was fully resolved within approximately 6 hours after detection.

Leadup

As part of the ongoing platform modernization effort, WBS Gantt-Chart for Jira version 3.0.0 introduced changes related to the migration from Atlassian Connect modules to Forge modules.

The release process for version 3.0.0 began on May 12, 2026. Validation in development, verification, and staging environments showed no issues prior to release. However, those environments did not contain data volumes comparable to the production environment.

Following the production rollout, an issue was discovered affecting access to the Gantt chart from the project page menu.

Fault

Users who manually upgraded to WBS Gantt-Chart for Jira version 3.x.x experienced a problem where the Gantt chart loading process stopped midway when accessing the application from the project page menu.

The problem was limited to a specific navigation path associated with the newly migrated Forge module integration. Accessing the Gantt chart through the Jira sidebar Apps menu remained fully functional.

The root technical issue was that the application logic executed against the production database did not adequately consider the significantly larger data volume present in production. This resulted in excessive processing time and incomplete loading behavior during initialization from the project menu context.

Impact

• Only customers who manually updated to version 3.x.x were affected.
• Users were unable to properly open Gantt charts from the project page menu.
• Alternative access through the Jira sidebar Apps menu remained available and functional throughout the incident.
• No data corruption or data loss occurred.
• Core Gantt chart functionality itself remained operational when accessed through unaffected navigation paths.

Recovery

After the issue was detected, the development team immediately began investigation and root cause analysis.

The team identified that the implementation introduced during the Connect-to-Forge migration did not scale appropriately for production-level data volumes. A corrective fix was developed and validated before deployment to production.

The fix was deployed to the production environment on May 13, 2026, and successful recovery was confirmed shortly afterward.

Timeline

Root Cause

The incident was caused by insufficient consideration of production-scale data volume during implementation of the Connect module to Forge module migration.

Although the functionality behaved correctly in verification and staging environments, those environments did not contain datasets equivalent to production. As a result, performance and execution characteristics under production conditions were not adequately validated prior to release.

Corrective Actions

Short-term:

• Implemented a fix to optimize processing for large production datasets.
• Deployed the corrective patch to the production environment immediately after validation.
• Confirmed that both project menu access and Apps menu access functioned correctly after deployment.
• Increased monitoring during the post-release period for version 3.x.x deployments.

Long-term:

• Improve pre-release validation by preparing staging environments with production-scale datasets.
• Introduce performance and scalability testing as part of the release validation process for major architectural migrations.
• Review all Connect-to-Forge migration implementations for similar scalability risks.
• Strengthen release checklists to include production-scale behavior verification for critical user flows.
• Enhance observability and logging around application initialization and navigation flows to accelerate future incident investigation.