epriestley a2b2c391a1 Distinguish between "Assigned" and "Effective" identity PHIDs more clearly and consistently ... Summary: Ref T13444. You can currently explicitly unassign an identity (useful if the matching algorithm is misfiring). However, this populates the "currentEffectiveUserPHID" with the "unassigned()" token, which mostly makes things more difficult. When an identity is explicitly unassigned, convert that into an explicit `null` in the effective user PHID. Then, realign "assigned" / "effective" language a bit. Previously, `withAssigneePHIDs(...)` actualy queried effective users, which was misleading. Finally, bulk up the list view a little bit to make testing slightly easier. Test Plan: - Unassigned an identity, ran migration, saw `currentEffectiveUserPHID` become `NULL` for the identity. - Unassigned a fresh identity, saw NULL. - Queried for various identities under the modified constraints. Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam Maniphest Tasks: T13444 Differential Revision: https://secure.phabricator.com/D20908		2019-11-19 09:37:44 -08:00
..
autopatches	Distinguish between "Assigned" and "Effective" identity PHIDs more clearly and consistently	2019-11-19 09:37:44 -08:00
patches	Make two ancient migrations fatal if they affect data	2019-02-06 17:08:34 -08:00
quickstart.sql	Update Quickstart SQL	2019-04-30 08:19:39 -07:00
stopwords.txt	Provide a setup warning about using the default MySQL stopword file	2014-08-13 15:34:09 -07:00
stopwords_myisam.txt	Show users how fulltext search queries are parsed and executed; don't query stopwords or short tokens	2017-04-12 19:07:54 -07:00