Page MenuHomePhabricator

When predicting project membership during edits, predict milestones will have parent membership
ClosedPublic

Authored by epriestley on Nov 19 2019, 6:52 AM.
Tags
None
Referenced Files
F17400083: D20920.diff
Sun, Jun 29, 7:11 AM
Unknown Object (File)
Thu, Jun 5, 4:44 PM
Unknown Object (File)
Sun, Jun 1, 8:40 AM
Unknown Object (File)
May 26 2025, 4:33 AM
Unknown Object (File)
May 8 2025, 10:52 PM
Unknown Object (File)
May 6 2025, 3:22 AM
Unknown Object (File)
Apr 29 2025, 3:38 AM
Unknown Object (File)
Apr 23 2025, 3:48 AM
Subscribers
None

Details

Summary

Depends on D20919. Ref T13462. When editing milestones, we currently predict they will have no members for policy evaluation purposes. This isn't the right rule.

Instead, predict that their membership will be the same as the parent project's membership, and pass this hint to the policy layer.

See T13462 for additional context and discussion.

Test Plan
  • Set project A's edit policy to "Project Members".
  • Joined project A.
  • Tried to create a milestone of project A.
    • Before: policy exception that the edit policy excludes me.
    • After: clean milestone creation.
  • As a non-member, tried to create a milestone. Received appropriate policy error.

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 Needs Review.Nov 19 2019, 7:07 AM
This revision was automatically updated to reflect the committed changes.