makeplane / makeplane/plane

[bug]: Issue List API ignores group_by parameter and returns flat array with null grouped_by

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

@vihar is already working on this.

Since Sep 4, 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 I issue a GET request to /api/v1/workspaces/<workspace_slug>/projects/<project_id>/issues/?group_by=state, the API ignores the group_by parameter, sets "grouped_by": null, and returns a flat array of issues.

json

{
  "grouped_by": null,
  "sub_grouped_by": null,
  "total_count": 1,
  "count": 1,
  "results": [
    {
      "id": "3316a9db-d234-42f0-8f49-d912d22f811a",
      "name": "Test Issue",
      "state": "ae9b8057-e219-497d-b547-9d73bc29934b",
      "labels": []
    }
  ]
}

Steps to reproduce

Create an issue in a project and assign it a state (e.g., Backlog).

Issue a GET request to the issues endpoint including ?group_by=state:

Bash

curl -X GET "http://127.0.0.1:8000/api/v1/workspaces/<workspace_slug>/projects/<project_id>/issues/?group_by=state" \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: <YOUR_API_KEY>

Observed Behavior
The API responds with HTTP 200, but "grouped_by" remains null and the results array is returned as a standard flat list:

JSON

{
  "grouped_by": null,
  "sub_grouped_by": null,
  "total_count": 1,
  "count": 1,
  "results": [
    {
      "id": "3316a9db-d234-42f0-8f49-d912d22f811a",
      "name": "Test Issue",
      "state": "ae9b8057-e219-497d-b547-9d73bc29934b",
      "labels": [...]
    }
  ]
}
Environment

Deploy preview

Browser

Google Chrome

Edition

Community

Version

v0.17.0-dev

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.