Native priority field vs custom priority fields

[lpb]

I encourage my clients to avoid the native Priority field for the same reasons you mention (and to avoid those other native fields that can be replaced by your own versions). You will only stand to gain; nothing to lose except the time for the one-time effort to convert.

Unrelated to the native vs. custom aspect, but regarding the nature of the Priority field itself, you may want to consider my suggestions here for another alternative in certain circumstances:

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 …

Thanks,

Larry