Yes, of course! I’ll be sharing one this week since a few people asked ![]()
Hi @Esteban_Giannini, do you by chance have a recording or screen shots yet? I am eager to see your example and I don’t know if I missed it.
A custom field (Ticket ID) that lives in the hidden project
This update has significantly hindered my team’s workflow in the following ways:
-
Increased Friction: Previously, I could view the “Priority” field with 1 click. Now, it requires 3 clicks to surface the same information for subtasks.
-
Wasted Efficiency: This change has led to an estimated 30% extra time wasted on triaging daily updates, which is unsustainable for a fast-paced environment.
-
Operational Risk: Because these fields are hidden, there is a high risk of missing critical priority levels, potentially leading to project delays.
Welcome, @Ace4,
What update are you referring to? This topic is a Community Tips > Forum Leader tips from one Forum Leader about a workflow approach, not about a particular Asana update, so that’s why I’m asking, and should make it easier to see if there’s anything we can offer to help.
Thanks,
Larry