makeplane / makeplane/plane

[feature]: Add work item custom properties to /work-items/ API response

Open
#8,654 3 comments 1 reaction 2 assignees View on GitHub

@vihar is already working on this.

Since Feb 22, 2026.

✨feature 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
Summary

I have created some custom work item properties so that I can leverage them via some automated processes. However, I've just discovered the number of steps it takes with different API endpoints just to retrieve a single custom property value.

If I have this wrong and there's a better way to do it, I'm all ears

  1. Call list all work items API
  2. For each work item, use the work item type Id to call the List custom properties endpoint
  3. For each custom property, call the custom property values endpoint to retrieve the value

So let's say for example I have a work item type with 2 custom properties. That means if I want to retrieve the "standard" properties as well as the custom ones for a single work item, I have to make 4 separate API calls to retrieve that value

  1. GET /work-items
  2. GET /work-item-types/{type_id}/work-item-properties
  3. GET /work-item-properties/{property_id_1}/values
  4. GET /work-item-properties/{property_id_2}/values

Can there not just be a "custom_properties" object array that is attached to the response when you call GET /work-items ? That seems to be far more efficient

Why should this be worked on?

If you want more people to utilize custom properties you need to make them easier to programmatically retrieve

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.