Configure Custom Fields in Asana
Add custom fields for decisions your project repeatedly needs to make. Use shared library fields when consistent cross-project reporting matters, rather than creating a new definition in each project.
Step-by-step guide
Check access and scope
Custom fields require a supported plan and suitable project or field permissions. Agree on names, value meanings and ownership first.
Choose useful field questions
List the review questions a field must answer.
Add the field type
Add the field through Customize and choose an appropriate type. Customize > Fields lets you add a field or select an existing definition; a library field can be reused across projects.
- Worked example: Use Readiness with Not started, Needs evidence and Verified. Keep Priority separate so an urgent task does not appear ready merely because it is important.
Reuse maintained definitions
Use an existing library field when the definition already exists.
Explain values with samples
Document allowed values and populate representative tasks.
Inspect missing values
Filter or chart the field and inspect missing values.
Verify the result
Two projects using the shared field interpret the same value consistently and exceptions remain discoverable.
Common mistakes
Check the handoff edge case
Creating a second Priority field with different values produces misleading comparisons. Reuse a maintained definition when semantics should match.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.