Feature #16523
RESTful API: Expose custom fields project relations
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | REST API | |||
| Target version: | - | |||
| Resolution: |
Description
- it is impossible so far to know what custom fields is assigned to a project (only to the tracker)
A custom field can be activated on a tracker depending or which project the issue is filed on. In the /project/ID/custom_fields.xml request, all you get is a list of trackers the custom fields is assigned to, but not the list of projects it is assigned.
just like #16522, this also prevents the issue structure to be fully discovered automatically.
(BTW I also started a forum post about this: )
Related issues
History
#1
Updated by Toshi MARUYAMA about 6 years ago
- Related to Feature #16522: RESTful API: Expose tracker standard fields assignments added
#2
Updated by Frederick Thomssen about 4 years ago
+1 to extend the API
#3
Updated by Toshi MARUYAMA almost 4 years ago
- Description updated (diff)
#4
Updated by Scott Little almost 3 years ago
I also would like to extend the API to have this information.
To be more precise about the description, at least for me (and I think the original poster) — what needs to be exposed is the issue custom fields that are relevant for a project.
For me, it would actually be appropriate to have one the following values on the `custom_fields.:format` API result:
all_projects: [true|false]
project_ids: [list of ids]