Page MenuHomePhabricator
Create Task
Maniphest T6114

Maniphest policies for Custom Fields
Closed, WontfixPublic
Actions

Description

Quite frequently, custom fields have a specialized use and you don't want to allow the majority of users to edit them. Just like you can set policies for "Can Edit Task Projects" or "Can Edit Task Status", it would be useful to have "Can edit (custom field)" for every custom field in use.

A beneficial side effect of setting this policy is that we could keep a simple and clean form for the majority of usesrs to create new Maniphest tasks, leaving i.e. "Story points" only to those that will do something about them.

Related Objects

Event Timeline

qgil created this task.Sep 17 2014, 3:09 PM
qgil raised the priority of this task from to Needs Triage.
qgil updated the task description. (Show Details)
qgil added projects: Maniphest, Custom Fields, Wikimedia.
qgil moved this task from Backlog to Important on the Wikimedia board.
qgil added subscribers: aklapper, 20after4, • ghost.of.chasemp.
qgil added a subscriber: qgil.
aklapper added a comment.Sep 17 2014, 3:55 PM

Another usecase: For tickets imported from previous tracking systems into Phabricator, we drop the IDs from the previous system into a custom field (and use that for URL redirects to Phabricator).
In theory that custom field should not be edited.

cburroughs added a subscriber: cburroughs.Sep 17 2014, 4:52 PM

For the import use case custom fields already have an edit boolean which might get you most of the way there.

epriestley triaged this task as Wishlist priority.Sep 18 2014, 12:33 AM
epriestley added a subscriber: epriestley.

Per @cburroughs, fields which can not be edited at all are already supported.

We are very unlikely to pursue per-field permissions. It opens up a huge amount of product complexity to support use cases that most installs either do not have, or which can reasonably solve culturally (i.e., ask people not to edit things). We have seen only a passing interest in these use cases from other installs.

It's also possible to implement "Advanced Custom Fields" which have arbitrary policy rules:

https://secure.phabricator.com/book/phabricator/article/custom_fields/#advanced-custom-fields

epriestley mentioned this in T5805: Make custom field visibilty dependent on custom task type field.Sep 18 2014, 12:35 AM
qgil closed this task as Wontfix.Dec 4 2014, 12:33 PM
qgil claimed this task.
In T6114#76219, @epriestley wrote:

It's also possible to implement "Advanced Custom Fields" which have arbitrary policy rules:

https://secure.phabricator.com/book/phabricator/article/custom_fields/#advanced-custom-fields

Wontfixing myself, since the reply makes total sense. Also because the truth is that until know we have avoided this need in Wikimedia.

Phabricator · Built by Phacility