epriestley 389e4d1b1f Lock milestone projects to an automatic color/icon ... Summary: Ref T10010. Currently, milestone subproject have editable icons/colors, but I don't think this is likely to be used much (the expectation is that milestones will be common and homogenous, and it doesn't make much sense to pick different icons for "Sprint 32" vs "Sprint 33", I think). Locking the icon and color lets us simplify the form, make milestones more distinct, and potentially reuse the color later for other things (e.g., active/future/past or on time / overdue or whatever else) or just give them a special color to make them more visible. The best argument for retaining this that I can come up with is that certain milestones may be special (e.g., Sprint 19 is a major release?), but you can just name it "Sprint 19 (v3.0!)" or something, which seems pretty good for now. Also don't show milestones on task browse/list view. Test Plan: {F1048532} Reviewers: chad Reviewed By: chad Maniphest Tasks: T10010 Differential Revision: https://secure.phabricator.com/D14912		2015-12-30 14:42:50 -08:00
..
PhabricatorProjectEditEngine.php	Lock milestone projects to an automatic color/icon	2015-12-30 14:42:50 -08:00