Defect #18875


[Rest API][custom field]Why "GET /custom_fields.xml" required the System manager's privilege?

Added by Hiroyuki Arakawa over 9 years ago. Updated almost 3 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected version:


Dear developers

Why Getting "Custom_field's Possible values" required the System manager's privilege?

I am creating a Redmine client by C#.
My Redmine project have Custom Field as List Format.

My C#'s Client can get Custom Field value,but can not update Custom Field.
Becase Getting "Possible values" required the System manager's privilege.

I can not give the system administrator privileges to all users.
I want all user to be able to get Possible values.

Best Regards.


Related issues

Has duplicate Redmine - Feature #25542: Custom Fields available over the APIClosed

Actions #1

Updated by Mischa The Evil about 9 years ago

  • Priority changed from High to Normal

My basic view on this is that the API implementation - r12165 for #11159 - just follows the same authorization level (user designated as an administrator) as is in use for its HTML counterpart. Global custom field listings are only available to administrator users via the Administration -> Custom fields menu.
Just to be sure: if you are trying to achieve updates for issues which are using custom field values, then see Rest_Issues#Updating-an-issue and Rest_api#Working-with-custom-fields.

Actions #2

Updated by Ieuan Jenkins over 8 years ago

I can see the logic behind permitting the same access level to the API implementation of the Custom Fields page as to the standard web view, but practically speaking it doesn't really work.

As an API user how am I supposed to know what a valid value is?

If we agree it's bad practice to permit RO access for non-admin users to the page, what about adding an include parameter option of custom_field_details, e.g. This could return a XML/JSON representation of the custom fields valid for that project/issue combination?

Actions #3

Updated by Loic Dachary over 8 years ago

It is very inconvenient to not be able to list the custom fields. When creating an issue, the id of the custom field is required to set the value and there is no other way to get it. So +1 on fixing this :-)

Actions #4

Updated by Justin Hill over 8 years ago

+1 on fixing this! I'm building an iOS client for Redmine and it's currently just not possible to retrieve the possible values for a custom field, which makes it impossible to implement a fully-featured issue composer.

Actions #5

Updated by Justin Hill over 8 years ago

Hmm, another thought on the implementation of this fix. Each tracker can have its own composition of custom fields, so while it would be somewhat helpful to have the possible values, we would also need to know which trackers use each field in order to allow a user to construct a valid edit.

Actions #6

Updated by ume san almost 8 years ago

like 'Issue Statuses', 'Trackers'.

Actions #7

Updated by Toshi MARUYAMA almost 7 years ago

  • Has duplicate Feature #25542: Custom Fields available over the API added
Actions #8

Updated by ume san over 5 years ago

I have created a patch for only 'Issue custom fields' of the project.

GET /projects/[id].xml?include=issue_custom_fields

Added Parameter issue_custom_fields to 'Showing a project' (GET /projects/[id].xml).

I would like to get your feedback.

Actions #9

Updated by Yuuki NARA over 5 years ago

+1 for #note-8 and #note-2 proposal

I agree that the items that can be referred to only by the setting screen of administrator should not be displayed other than administrator.

However, what kind of problems will occur if you allow reference to custom field items beyond administrator?

It is necessary to think about whether the current access authority and the screen composition specification are appropriate.

For the tracker's required custom field currently selected in the project and the selected custom field,
It is a practical countermeasure to make it possible for project members to refer to possible values.

Sorry, the following is Japanese.




Actions #10

Updated by Loic Dachary almost 3 years ago

I know I already commented on this one five years ago but here it is again, as I ran into this it today :-)


Also available in: Atom PDF