makeplane / makeplane/plane

[bug]: Frontend calls /advance-analytics endpoints on Community Edition resulting in 500 Internal Server Error

Open
#9,237 1 comment 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Jun 15, 2026.

🐛bug plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior

When using the Plane Community Edition (deployed via Helm Chart v1.5.0/v1.5.1), navigating to a workspace or project and clicking on the Analytics tab causes the UI to break.

Checking the browser's developer console and the API pod logs reveals that the frontend is attempting to call endpoints that are either unavailable or failing in the Community Edition backend, such as:

/api/workspaces//advance-analytics?tab=work-items
/advance-analytics-stats
/advance-analytics-charts

These requests return a 500 Internal Server Error (or 404 Not Found), which causes an unhandled exception in the frontend UI.

Expected Behavior: Since Advanced Analytics is a Pro/Commercial feature, the Community Edition frontend should either:

Hide the "Analytics" tab completely to prevent users from accessing unsupported endpoints.
Gracefully handle the absence of the feature by showing an "Upgrade to Pro" empty state instead of making API calls that result in a 500 error.
The backend should return a 403 Forbidden or 501 Not Implemented with a clear message rather than crashing with a 500 Internal Server Error.

Environment details:

Plane Version: Community Edition v1.5.1 (or v1.5.0)
Deployment method: Kubernetes (Helm Chart)
OS: Linux

P.D. It seems this UI issue was introduced after PR #6973 added the frontend calls, but the endpoints are missing in the CE backend.

Steps to reproduce
  • Deploy Plane Community Edition using the official Helm chart.
  • Log in and navigate to a Workspace or Project.
  • Click on the "Analytics" tab.
  • Open the browser's Network/Console tab to see the 500 Internal Server Error on the advance-analytics endpoints.
Environment

Production

Browser

None

Variant

Self-hosted

Version

Community Edition v1.5.1 (or v1.5.0)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.