How to Add Custom Fields in Asana (Complete Step-by-Step Guide)

Most teams use Asana the same way — tasks, due dates, assignees. And then they hit a wall.

They need to track deal size. Or project stage. Or which region a campaign belongs to. And suddenly, the default fields just don’t cut it.

That’s exactly where custom fields come in.

Custom fields let you capture the data that actually matters to your workflow — not just the generic stuff Asana ships with. According to Asana’s own research, teams that customize their project workflows report 45% fewer missed deadlines and spend significantly less time hunting for status updates in Slack threads.

This guide walks you through exactly how to add custom fields in Asana, what types are available, when to use each one, and how to build a setup that your whole team actually sticks to.

What Are Custom Fields in Asana?

Custom fields are additional data columns you attach to tasks or projects in Asana. Think of them as extra properties you define yourself — because Asana’s default fields (assignee, due date, description) rarely capture everything a real workflow needs.

With custom fields, you can track things like:

• Priority level (High / Medium / Low)
• Budget (numeric dollar value)
• Pipeline stage (Prospecting → Qualified → Proposal → Closed)
• Estimated hours (for resource planning)
• Region or territory (for multi-market teams)
• Approval status (Pending / Approved / Rejected)

According to a 2023 project management survey by Wellingtone, 77% of high-performing project teams use custom data tracking to monitor work — compared to just 40% of underperforming ones. The difference isn’t talent. It’s visibility.

Who Can Add Custom Fields in Asana?

Before you dive in, a quick note on access:

• Free plan users: Custom fields are not available on Asana’s free tier.
• Premium, Business, and Enterprise plans: Full access to custom fields.
• Guest users: Cannot create or edit custom fields — only view them.
• Admin/Member roles: Any full member on a paid plan can create custom fields within projects they have edit access to.

If you’re on a free plan and hitting this wall frequently, it’s one of the clearest signals to upgrade — Asana Premium starts at around $10.99 per user per month (billed annually).

How to Add Custom Fields in Asana

There are two main ways to add custom fields — directly inside a project, or from Asana’s custom fields library. Here’s how both work.

Adding Custom Fields From Inside a Project

This is the fastest method when you’re building a project from scratch or adding fields on the fly.

Step 1: Open your project

Navigate to the project where you want to add custom fields. Make sure you’re in List view or Board view — custom fields are most visible here.

Step 2: Click the “+” icon in the column header

In List view, look for the “+” button at the far right of the column headers (next to fields like Assignee, Due Date). Click it.

Step 3: Select “Add Custom Field”

A dropdown will appear with existing fields from your organization’s library. At the bottom, you’ll see the option to “Create Custom Field.” Click that.

Step 4: Choose your field type

Asana will prompt you to select a field type. You have six options (covered in detail in the next section). Pick the one that fits your use case.

Step 5: Name your field and configure options

Give the field a clear, specific name. If you’re creating a dropdown, add your options now. You can also choose a color for each option to make scanning easier.

Step 6: Click “Create Field”

Your custom field now appears as a column in your project. You can immediately start filling it in across your tasks.

Adding Custom Fields From the Fields Library

If your organization has already built a library of shared fields, this is the smarter approach — it keeps your data consistent across projects.

Step 1: Go to project settings

Click the three-dot menu (⋯) at the top right of your project, then select “Fields.”

Step 2: Browse or search the library

You’ll see all custom fields that have been created in your workspace. Search by name or scroll to find what you need.

Step 3: Toggle the field on

Flip the toggle next to any field to add it to your current project. It’s that simple — no duplication, just a shared field now living in your project too.

Step 4: Customize display settings

After adding, you can drag to reorder fields in your project view, or hide fields you don’t need visible right now without deleting them.

The Six Types of Custom Fields in Asana

Choosing the right field type matters. Here’s a breakdown of each one and when to use it.

Text

A free-form text box. Use it for notes, links, short descriptions, or any data that doesn’t fit a fixed format.

Best for: Client contact info, notes field, custom IDs, or any freeform input.

Watch out: Text fields are hard to filter or sort by. Use sparingly — they don’t lend themselves to reporting.

Number

A numeric field. Can be formatted as a plain number, a currency value (with dollar/euro/pound symbols), or a percentage.

Best for: Budget tracking, estimated hours, deal size, conversion rates, or any measurable metric.

Pro tip: Use the currency format for anything financial — it keeps your data clean for rollups and reporting in Asana’s Portfolio view.

Dropdown (Single-Select)

A fixed list of options where users pick exactly one. This is the most widely used custom field type in Asana.

Best for: Status fields (In Progress / Blocked / Complete), priority levels, approval stages, or category tags.

Why it works: Dropdown fields are filterable, sortable, and perfect for building board views that map to your process stages.

Multi-Select

Like a dropdown, but users can choose multiple options at once.

Best for: Tagging tasks with multiple categories, skills required, channels involved, or any attribute that can have more than one value.

Watch out: Multi-select fields are harder to sort and report on. Use them for tagging and categorization, not for core workflow stages.

Date

A date picker tied to a specific task.

Best for: Tracking contract dates, review deadlines, kickoff dates, or any secondary date beyond the built-in due date.

Note: This is separate from Asana’s built-in Due Date field — custom date fields let you capture additional dates within the same task.

People

Links directly to Asana users or team members.

Best for: Tracking secondary owners (e.g., a reviewer vs. a primary assignee), stakeholders, or account contacts.

How to Edit or Delete Custom Fields

Need to update a field after you’ve created it? Here’s how.

To edit a custom field:

1. Click the field name in the column header
2. Select “Edit field”
3. Update the name, options, or formatting
4. Click “Save”

Important: Edits to shared fields update them across all projects that use them. If a field is only in one project, changes stay local.

To delete a custom field from a project (without deleting it globally):

1. Go to project settings → Fields
2. Toggle the field off

This removes it from the project view but preserves it in the library.

To permanently delete a custom field:

1. Navigate to your organization’s Custom Fields Library (via the main navigation sidebar under your workspace name)
2. Find the field
3. Click the three-dot menu → “Delete field”

Note that deleting a field removes all data stored in it across every project. There’s no undo. Export or document that data before you delete.

How to Use Custom Fields in Rules and Automations

Here’s where custom fields become genuinely powerful — you can use them to trigger automations.

For example:

• When Priority = High → automatically assign to a specific person
• When Stage = Approved → move task to the next section
• When Budget exceeds a certain number → send a notification

To set this up:

1. Click “Customize” in the top right of your project
2. Select “Rules”
3. Click “Add Rule” → “Create custom rule”
4. Set your trigger condition using a custom field value
5. Define the action Asana should take
6. Save the rule

Asana reports that teams using workflow automation save an average of 257 hours per year per employee — nearly 30 full working days. Connecting custom fields to rules is one of the highest-leverage things you can do inside the platform.

How to Report on Custom Fields

Creating the field is step one. Actually using the data is where it pays off.

Filtering by custom field:

In List or Board view, click “Filter” at the top of your project. You can filter tasks by any custom field value — for example, showing only tasks where Priority = High.

Sorting by custom field:

Click “Sort” and select your custom field. Number and date fields sort numerically/chronologically. Dropdown fields sort alphabetically by default.

Reporting in Portfolios and Workload:

If you’re on Asana Business or Enterprise, Portfolios let you roll up custom field data across multiple projects. This is especially useful for tracking budget vs. actuals, pipeline stages, or resource allocation across an entire program.

Exporting data:

Go to project settings → Export/Print → Export as CSV. All custom fields are included in the export, making it easy to analyze in Excel or Google Sheets.

Best Practices for Custom Fields That Actually Get Used

Custom fields only work if your team fills them in. Here are the principles that separate teams with clean, useful data from teams with half-empty columns nobody trusts.

Keep the list short. Teams with fewer than 6 custom fields per project see dramatically higher fill rates than teams with 10+. Every field you add is a question your team has to answer on every task. Be ruthless.

Name fields like questions. “Priority” is vague. “How urgent is this?” is clearer. The field name is the prompt your team sees — make it obvious what the right answer looks like.

Make dropdowns exhaustive but not overwhelming. If your dropdown has 12 options, no one will pick the right one consistently. Aim for 3–6 clear choices with distinct meanings.

Use shared fields from the library. If “Priority” means different things in different projects, your data is useless for cross-project reporting. Standardize on shared fields wherever possible.

Audit fields quarterly. Fields that nobody fills in for 30+ days should be removed or redesigned. Asana’s reporting dashboard shows field completion rates — use it.

Common Mistakes to Avoid

Creating duplicate fields. “Priority,” “Priority Level,” and “Task Priority” are three different fields in three different projects that all mean the same thing. Use the shared library.

Using text fields for structured data. If you’re typing “High,” “Medium,” or “Low” into a text field, you’re doing it wrong. That’s a dropdown. Text fields can’t be filtered or reported on.

Treating custom fields as a substitute for good task names. Fields support a task — they don’t replace a clear, actionable title. A task called “Review” with a status of “In Progress” tells your team nothing.

Overcomplicating new team members’ onboarding. A 15-field project template is a great way to ensure new joiners fill in nothing correctly. Start lean, add fields when the need is proven.

Conclusion

Custom fields are one of the most underused levers in Asana. Most teams set them up once, add too many of them, and then watch fill rates crater after week two.

The teams that get it right do three things differently: they start with fewer fields than they think they need, they use shared library fields to keep data consistent, and they connect fields to automations so the data actually drives action — not just reporting.

Start with one or two fields on your most important project. See what data your team actually fills in without being asked. Build from there.

And when you’re ready to bring that same systematic, data-driven thinking to your outbound pipeline — SalesSo is ready to build it with you.