Because custom fields can contain things like time spent, time estimated, budget, cost, hourly rate… There is a wide range of risky fields people use, so to me it was a smart move to release the read-only feature without field and then work on the ability to pick the fields you want to show (instead of not releasing anything until everything is ready). We discuss this lean way of releasing features in 🦄 If Wishes Were Unicorns: Why Asana Might Not Have Implemented that Feature Request (and other thoughts about Asana feature development and product strategy)
1 Like