epriestley 04186e02cf Separate handle "status" and "availability" ... Summary: Ref T7707. Handles currently have a "status" field and a "disabled" field. The "status" field has these possible values: "open", "closed", "1", "2". durp durp durp Instead, do: - status = <open, closed> - availability = <full, partial, none, disabled> I think these make more sense? And are a bit more general? And use the same kind of constants for all values! Test Plan: Looked at all affected handles in all states (probably). Reviewers: chad, btrahan Reviewed By: btrahan Subscribers: epriestley Maniphest Tasks: T7707 Differential Revision: https://secure.phabricator.com/D12832		2015-05-14 11:14:44 -07:00
..
application	Remove getIconName from all applications	2015-01-30 12:11:21 -08:00
config	Add getGroup to ConfigOptions	2015-02-09 13:10:56 -08:00
constants	Remove @group annotations	2014-07-10 08:12:48 +10:00
controller	Use PhutilInvalidStateException	2015-05-14 07:53:52 +10:00
engine	Use PhutilInvalidStateException	2015-05-14 07:53:52 +10:00
index	Build a Conpherence thread index	2015-01-06 10:24:30 -08:00
interface	Provide PhabricatorSavedQuery to renderResultsList()	2013-07-03 05:46:04 -07:00
management	Fix bad ancestor classname	2015-01-07 16:13:20 -08:00
query	Add an anyone() typeahead function for matching any document owner	2015-04-23 15:44:27 -07:00
selector	Rename PhabricatorSearchEngine subclasses	2015-05-04 12:21:54 +10:00
storage	Fix visiblity of LiskDAO::getConfiguration()	2015-01-14 06:54:13 +11:00
typeahead	Use typeaheads instead of checkbox lists for task status / priority	2015-04-23 11:49:34 -07:00
view	Separate handle "status" and "availability"	2015-05-14 11:14:44 -07:00
worker	Fix visibility of the PhabricatorWorker::doWork() methods	2015-01-16 06:58:50 +11:00