When an edit overrides an object lock, note it in the transaction record
ClosedPublic
Actions

Authored by epriestley on Feb 8 2019, 12:20 AM.

Details

Reviewers

amckinley

Maniphest Tasks

T13244: 2019 Week 6 Bonus Content

Commits

rPa20f10803412: When an edit overrides an object lock, note it in the transaction record

Summary

Ref T13244. See PHI1059. When you lock a task, users who can edit the task can currently override the lock by using "Edit Task" if they confirm that they want to do this.

Mark these edits with an emblem, similar to the "MFA" and "Silent" emblems, so it's clear that they may have bent the rules.

Also, make the "MFA" and "Silent" emblems more easily visible.

Test Plan

Edited a locked task, overrode the lock, got marked for it.

Screen Shot 2019-02-07 at 4.14.09 PM.png (157×317 px, 6 KB)

Diff Detail

Repository

rP Phabricator

Branch

lock1

Lint

Lint Passed

Unit

Tests Passed

Build Status

Buildable 21905
Build 29904: Run Core Tests
Build 29903: arc lint + arc unit

Unit TestsFailed
View All

	Time	Test
	291 ms	PhabricatorProjectCoreTestCase::Unknown Unit Message ("") EXCEPTION (PhabricatorDataNotAttachedException): Attempting to access attached data on PhabricatorProject, but the data is not actually attached. Before accessing attachable data on an object, you must load and attach it. Data is normally attached by calling the corresponding needX() method on the Query class when the object is loaded. You can also call the corresponding attachX() method explicitly.
	402 ms	PhabricatorProjectCoreTestCase::Unknown Unit Message ("") EXCEPTION (PhabricatorDataNotAttachedException): Attempting to access attached data on PhabricatorProject, but the data is not actually attached. Before accessing attachable data on an object, you must load and attach it. Data is normally attached by calling the corresponding needX() method on the Query class when the object is loaded. You can also call the corresponding attachX() method explicitly.
	1 ms	AlmanacNamesTestCase::Unknown Unit Message ("") 30 assertions passed.
	0 ms	AlmanacServiceTypeTestCase::Unknown Unit Message ("") 1 assertion passed.
	0 ms	AphrontHTTPSinkTestCase::Unknown Unit Message ("") 2 assertions passed.
		View Full Test Results (2 Failed · 373 Passed)

Event Timeline

epriestley created this revision.Feb 8 2019, 12:20 AM

Harbormaster returned this revision to the author for changes because remote builds failed.Feb 8 2019, 12:22 AM

Harbormaster failed remote builds in B21905: Diff 48068!

Tailor the interaction check to avoid some complications in Projects unit tests, where membership is sometimes not fully loaded and we're editing on behalf of some random actor.

Harbormaster completed remote builds in B21906: Diff 48069.Feb 8 2019, 12:46 AM

epriestley requested review of this revision.Feb 8 2019, 12:46 AM

aeiser added a subscriber: aeiser.Feb 8 2019, 1:17 AM

Wasn't there supposed to be an icon getting upstreamed in this revision? I can see the change to the celerity map but not the associated icon file.

src/applications/transactions/view/PhabricatorApplicationTransactionView.php
420	I'm pretty sure this was not what you meant, since `$lock` isn't used again in this function and I've never seen the "use assignment operation's side effect as a function argument" idiom in the Phabricator code base.