Page MenuHomePhabricator

When a field isn't lockable, just freeze the lock status instead of removing any lock
ClosedPublic

Authored by epriestley on Nov 17 2016, 10:52 PM.
Tags
None
Referenced Files
F18986556: D16895.id40671.diff
Nov 17 2025, 3:18 PM
F18853967: D16895.id40671.diff
Oct 31 2025, 9:03 PM
F18847194: D16895.id.diff
Oct 29 2025, 11:17 PM
F18841484: D16895.diff
Oct 28 2025, 9:33 AM
F18595962: D16895.id.diff
Sep 12 2025, 11:17 PM
F18583055: D16895.diff
Sep 11 2025, 9:22 AM
F18422185: D16895.diff
Aug 30 2025, 5:49 PM
F18102268: D16895.id40672.diff
Aug 9 2025, 7:36 PM
Subscribers
None

Details

Summary

See downstream issue here: https://phabricator.wikimedia.org/T150992

In at least one case (project milestones) we have a locked, non-lockable field. This means "this is locked, and you can't change the fact that it is locked".

At least for now, preserve this behavior.

Test Plan

Created a new milestone of an existing project. This worked correctly with the patch.

Diff Detail

Repository
rP Phabricator
Branch
milestone1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 14561
Build 18996: Run Core Tests
Build 18995: arc lint + arc unit

Event Timeline

epriestley retitled this revision from to When a field isn't lockable, just freeze the lock status instead of removing any lock.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Nov 17 2016, 10:53 PM
This revision was automatically updated to reflect the committed changes.