Track key attributes with a simple ✔ "Boolean" custom field (instead of Yes | No)

[lpb]

@Bastien_Siebman

why having a single level of priority is probably a good idea (for a lot of reasons)

Isn’t that the same as my earlier Forum Leaders tips I linked to above?:

Don't use a "Priority" custom field (usually); use a simpler approach, or a "Critical" instead

I’m not a fan of the Priority custom field! Nine out of ten times I see it used by clients, I feel they’re wasting time and recommend they remove or replace it. A Priority field is shown in many Asana demo videos and is included by default in many Asana-provided project templates. I feel most of these are not optimal. Simpler Approaches In cases where a task has a Due date set, a Priority custom field often is redundant; the Due date effectively conveys the priority, so a custom field is not …