Atlassian VS Code Extension: Bug Tickets Open as Blank Issue View

[rafistrauss]

Describe the bug

In VS Code, the Atlassian extension fails to render some Jira issues in the issue details webview. Clicking an affected ticket starts loading, then the panel stays blank. Other Jira actions (such as transitioning the same ticket) still work.

In our case, this appears to happen only for bug-type tickets in this project.

The failure appears tied to Atlaskit editor/feature-gate initialization and then crashes while rendering ADF content.

To Reproduce

1. Open VS Code with Atlassian extension version 4.0.28 installed. (v4.0.27 also presented the issue)
2. Connect to Jira Cloud and open the Atlassian issue view.
3. Click an affected bug ticket in this project.
4. Observe the webview loads and then shows no issue content.

Control check:

1. Click a different non-bug ticket in the same project.
2. Observe it may render successfully in the same session.

Expected behavior

Clicking any Jira issue should consistently render issue details in the VS Code webview, including bug-type tickets.

Actual behavior

For some issues, the webview fails to render and remains blank. DevTools shows errors including:

• Feature gate client initialization failure:
  • Client must be initialized before using this method
  • gateName: platform_editor_controls_increase_full_page_gutter
• React render failure:
  • Objects are not valid as a React child (found: object with keys {type, version, content})

Screenshots

Environment and Version (please complete the following information):

• Atlassian Plugin Version: 4.0.28
• Visual Studio Code Version (x.x.x): 1.120.0
• Is this a local or cloud environment? Local
  - If Cloud, Browser (chrome, safari)
• If Local, OS (macOS, windows, linux): macOS

Additional context

• Extension versions tested: Atlassian Atlascode 4.0.27/4.0.28
• Scope observed so far: issue reproduces on bug-type tickets in this project, while non-bug tickets open normally.
• A recurring log line appears for both working and broken tickets:
  • Could not fetch Jira development info, falling back to local data AxiosError: Request failed with status code 401
• That 401 appears to be a non-blocking fallback path, since it occurs for both successful and failed issue opens.
• Console also reports:
  • Multiple versions of FeatureGateClients found on the current page
  • currently bound version 0.0.0-development while module version 4.26.5 was loading
• Likely impact: issue-specific content (ADF document shape) hits a broken render path when feature-gated Atlaskit editor code does not initialize correctly.