I’ve used the built-in “Send feedback” to tell Asana what I like or dislike about the rolled-out feature. I don’t know which method is more effective… using the feedback feature or posting/voting on feedback in the forum.
We see this as a step forward toward better focus on fields that matter and appreciate that effort is being put in this direction. Here are a few quirks we don’t like:
- I noticed when opening something from the inbox, all fields are collapsed, even if that task is only part of one project. At least when you open it in context of a project, that project’s fields are visible. We feel that fields should not be completely collapsed by default when viewed from inbox. It should default to the expanded fields of:
- The project it’s nested in, if only nested within one project
- The project it was created in, if multi-homed in several projects
- The Estimated and Actual time fields have been a part of our established spaces for user support ticket management, development ticket management, project requests, etc. These are now collapsed and repeated only in projects that have those fields added.
- We feel these should remain static / visible on the task in one place, perhaps above Projects in the new order of things to reduce hunting for it.
- We noticed Actual Time was now missing from subtasks. We had to click to “Show inherited fields” to see any fields on a subtask and, when we did so, could only see Estimated Time and had no way to track actual time on the subtask (previously could and it rolled up into parent task’s actual).
- We agree with others here that the ability to quickly change the Section of any project is a lost feature that should be reinstated. Perhaps the new layout could show Project > Section > [number of fields], with the ability to click and change the section reinstated from the past.
We’ve long wanted to tailor the visible fields to the project where the task is currently being viewed. This is a good step. I’d be curious to see how Asana’s past field limits interact with these changes (List of technical and data limitations in Asana). (Looks like it will be lifted, according to @Garrett_Knoll.) We hated that we had no control over what order fields displayed as a task is multi-homed into more and more projects and eventually custom fields past ~50/60 would be simply not visible on the task. It looks like we’ll need to review what fields are added to projects to ensure people working in those projects can see what’s crucial to them without needing to expand fields of other projects. The thing we’ll keep dreaming for—the ability to tailor the field layout of the task… a “favorite” task design by project that would allow us to control how things appear when viewed in the context of that project. We’re thinking things like collecting certain fields that get grouped together with a colorful background, pinned to the top of fields everywhere or just this project, ability to bold some field names, etc. (noticed this comment, similarly dreaming, by @pdmcdermott : https://forum.asana.com/t/default-order-of-custom-fields-in-task/1064495/20)