Card #296 · Asana Apps & Integrations
Inefficient management and scaling of custom fields
Managing custom fields at scale is tedious due to the lack of retroactive application to existing projects and the inability to organize fields into sections. This leads to manual cleanup for admins and makes tasks overwhelmingly long and difficult to read when multihoming is used.
Pain score
0.71/ 1.00 · weighted product of four components
Reach0.72distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement1.00upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 4 verified quotes
there does not appear to be an easy way to apply that new field retroactively to projects that already exist. This creates a lot of manual cleanup when a company decides to standardize a new field across the organization.
with so many custom fields, task organization is harder to manage and tasks become overwhelmingly long and difficult to read at a glance.
If sections were introduced, teams from different departments could key in easily on where to look for information and where to input their work for a task.
This would save a significant amount of administrative time, especially for organizations using Asana at scale.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro