Redmine

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 http://redmine.org/custom_fields.json page, what about adding an include parameter option of custom_field_details, e.g. http://www.redmine.org/issues/18875.json?include=custom_field_details. This could return a XML/JSON representation of the custom fields valid for that project/issue combination?

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 :-)

+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.

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.

+1
like 'Issue Statuses', 'Trackers'.

+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.

administratorの設定画面のみで参照できる項目を、administrator以外に表示すべきで無いことについては合意する。

しかし、administrator以外にカスタムフィールド項目の参照を許可した場合、どのような問題が発生するのだろうか。
現在のアクセス権限と画面構成の仕様が適切であるかは、考えてみる必要があるのではないか。

プロジェクトで現在選択されているトラッカーの必須カスタムフィールド、及び選択されたカスタムフィールドに対して、
取り得る値をプロジェクトメンバーが参照可能とすることは、現実的な対応策と思う。

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