So I was planning to contact Asana to tell them we had a HUGE bug with our organization when I discovered with this topic that it is in reality a new “feature” ??? How can you team drop a bomb like this without notice @Marie ? Overnight the organization we spent months to build and implement has just became a complete mess…
Your whole solution is based on projects : each project is a dedicated space with his own features (members, custom fields, presentation, …) and tasks/subtasks are just supposed to be put in the right projects depending on your needs. This solution has its limitations but at least it is a good way to keep your organization clean an tidy : tasks only carries the information you want them to carry.
But now with this feature subtasks are drilling holes in the “walls” between projects. If I wanted a subtask to have the same fields as its parent I would have simply put it in the same project, or added those fields to the project were the subtask is ! Now my subtasks all carry useless fields which are meaningful ONLY for their parents. People in my organization are now lost as they are flooded with fields they don’t know/don’t need to use…
I understood the explanation given by @Phil_Seeman but I think the benefits of this update are by far outweighed by the disavantages, and I don’t understand how those were not anticipated. The only explanation I have is that maybe you have a bigger plan and you want to implement a solution like the one @JFrentz presented ? If that the case I can only support it as I already developed a custom application to synchronise tasks and subtasks custom fields across our organization and it is a major plus for our Asana experience. Having it native in Asana would be a blast, but if that is your plan please wait to release the full feature instead of releasing only the first step …
I’m a big supporter of Asana and a very enthusiastic user, but this time I am clearly disappointed by how this feature was handled 