Hoping this is a simple functionality I need direction on or possibly a feature request for the product team:
Once upon a time I recall Asana allowing adding annotations, notes, or edits directly onto images attached to tasks. This included being able to click on an area in the image to create a numerated subtask. I don’t seem to be able to do that now when testing.
This would be great to have more clarity to specifically point out specific areas in the screenshot image for our UX designer for example vs written instruction.
Thanks so much Larry ! We have the Entreprise plan, but when I open a png image in my task, I don’t see the Add Feedback option. I have seen it before but not sure when that changed. Is this an Admin setting to be updated ?
Also side note, I realize this function creates subtask for feedback.
In the web team, we decided that the team members prefer a flat view for their tasks, using main task level only vs subtasks, especially as we are trying to re-roll out asana to our team.
In this case, would you recommend any other workaround that I may not have considered for how to interact with our images to clarify a UX tax update? for ex. The ability to circle specific sections in the image
Never using subtasks is a very limiting decision in my view, and can cause other problems. Even clicking the list view expand arrow which shows the subtasks directly in the tasks list is not workable?
To avoid subtasks, you could just drag the created subtasks to the left into the tasks list and they’re converted from subtasks to tasks.
A hybrid approach is to select all the subtasks and add them to the project, making them both subtasks and top-level tasks; confusing, but then grouping under the parent is not lost.
Finally, third party proofing tools exist, some with Asana integrations.
Thanks Larry ! I’ll take a look at the troubleshooting steps .
The subtask vs flat main task was brought up based on our web team’s prior experience with using subtasks and having a hard time tracking their work. This is due to the last 2-3 years of our company experiencing poor roll out of asana and management. So far what’s worked is stripping down to foundational project set ups and implementing one active work project for all their in flight tasks, multihomed to their respective individual projects ,and viewing all collective tasks per individual in tabs as kanban boards, and keeping it as a flat main task for ease of adoption.
Most of the team voted for flat tasks vs one team member who enjoyed the branching logic of subtasks but for sake of uniformity we’ve decided to go with the majority. Perhaps subtasks can be introduced in the future. My prior experience of trying to implement subtasks in the marketing team also came across a large issue of change management and convoluted processes despite analog rules to auto populate hand off to assignees and triggered due dates. Definitely a learning process for me of where to push and pull! And for me a big learning curve of the tech team for hand off processes.. before I formulate any rules. baby steps !
