Page MenuHomePhabricator

Respect "disabled" custom field status granted by "subtype" configuration in form validation
ClosedPublic

Authored by epriestley on Aug 22 2019, 1:02 AM.
Tags
None
Referenced Files
F22773457: D20726.diff
Mon, Oct 5, 9:45 PM
F22749568: D20726.id.diff
Sun, Oct 4, 8:03 PM
F22744316: D20726.id49415.diff
Sun, Oct 4, 4:03 PM
Unknown Object (File)
Aug 14 2026, 2:01 AM
Unknown Object (File)
Aug 14 2026, 12:16 AM
Unknown Object (File)
Jun 20 2026, 7:04 PM
Unknown Object (File)
Jan 11 2026, 4:20 AM
Unknown Object (File)
Nov 30 2025, 5:18 AM
Subscribers
None

Details

Summary

Fixes T13384. Currently, the subtype "disabled" configuration is not respected when selecting fields for ROLE_EDIT.

The only meaningful caller for ROLE_EDIT is transaction validation, but transaction validation should respect fields being disabled by subtype configuration.

Test Plan
  • Added a "required" Maniphest custom field "F", then "disabled" it in a subtype "S".
  • Created a task of subtype "S".
    • Before: Form submission fails with error "F is required", even though the field is not actually visible on the form and can not be set.
    • After: Form submits cleanly and creates the task.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Draft.Aug 22 2019, 1:03 AM
This revision was landed with ongoing or failed builds.
This revision was automatically updated to reflect the committed changes.