# Bug OP-15158 - The available_projects api endpoint displays custom project fields incorrectly

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-15158

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 14.1.1 |
| Observed in versions | 14.0.0 |
| Sprint | 14.1.1 |
| Backlog bucket |  |
| Bug found in version (deprecated) | 14.0.x |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Attila Dombi |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Have a few projects and assign some project custom fields to the last project.

2.  Go to the `/api/v3/projects` endpoint.

3.  If the first project doesn't have any project custom fields activated, then none of the project will have custom fields returned from the api.

### What is the buggy behavior?

  - The projects returned do not contain any project custom fields if the first project in the list does not have custom fields activated.

### What is the expected behavior?

*Describe how the application should behave like. Example:*

1.  Each project has a set of project custom fields and those should  
    be returned for each project.
