Page MenuHomePhabricator

Don't show the "Override Lock" prompt when creating objects
ClosedPublic

Authored by epriestley on Mar 23 2017, 12:43 PM.
Tags
None
Referenced Files
F18252355: D17541.diff
Thu, Aug 21, 7:46 PM
F18094499: D17541.id.diff
Thu, Aug 7, 10:10 PM
F17847390: D17541.id.diff
Jul 27 2025, 6:06 AM
F17843646: D17541.id42187.diff
Jul 27 2025, 1:10 AM
F17840375: D17541.id42189.diff
Jul 26 2025, 9:05 PM
F17839863: D17541.diff
Jul 26 2025, 8:31 PM
F17827335: D17541.id.diff
Jul 26 2025, 8:09 AM
F17818454: D17541.diff
Jul 26 2025, 12:24 AM

Details

Summary

Fixes T12369. When you create objects they may technically be locked: either because the default state is legitimately locked, or because the default policies prevent you from viewing so we sort of technically end in a locked state.

Regardless, don't prompt during creation, since this prompt isn't useful even if the lock detection is completely legitimate.

Test Plan
  • In ApplicationsManiphestConfigure, set "Default View Policy" to "No One".
  • Tried to create a task.
  • Before patch: prompted to override lock.
  • After patch: no override prompt.

Diff Detail

Repository
rP Phabricator
Branch
task1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 16102
Build 21367: Run Core Tests
Build 21366: arc lint + arc unit

Event Timeline

Done that manually but test didn't pass. Only way on new task to not show Locked message is to apply policy as fallows:

Default View Policy All Users 
Default Edit Policy Subscribers
This revision is now accepted and ready to land.Mar 23 2017, 1:37 PM

@d.maznekov If you believe this patch doesn't completely resolve the issue, please wait for it to land, upgrade to HEAD of master so your install has the change, then file a new bug report with clear, complete reproduction instructions which allow us to reproduce the issue you're seeing on a fresh install of Phabricator. Anything other than complete reproduction instructions will not result in upstream changes.

This revision was automatically updated to reflect the committed changes.

FWIW I patched this locally and it fixes the scenarios I've seen this issue.