That didn’t take long. After spending a few days with Asana my team decided that they could not work with that project management tool. After spending several hours on training email, live screen casting, and phone calls I agree.
Deal Breaker : No HTML Formatting
One BIG issue was the complete lack of HTML formatting including inline image retention and CSS styling of content that is pasted into discussions and descriptions. Asana has the annoying habit of stripping any-and-all HTML elements down to bare text. Cleaner and more consistent interface? Sure? Boring as heck, hell yes. LOSING CRITICAL ELEMENTS like charts and graphs that were part of the original content? A deal breaker.
Asana’s response to that issue:
ChrisNOV 11, 2014 | 05:23PM PSTHi Lance,
Thanks for the request for HTML formatting and hyperlinks in discussions of Asana. We don’t have these additions planned for the near term, but we will note your suggestion to help inform future product developments.
We appreciate knowing what you think about the product. Let me know if I can help you with anything else.Thanks,
No Project-Level Documents or Discussions
TerrenceNOV 10, 2014 | 03:39PM PSTHi Lance,
Thank you for writing in with your request for project-level attachments. We don’t have that functionality at this time. I will note your feedback for the product team to consider.
As a workaround, you can also find all attachments across multiple projects using Search Views (https://asana.com/guide/learn/basics/search#gl-search-views).
Please let me know if you have any other questions or suggestions.Thanks,
The Other Stuff
TerrenceNOV 11, 2014 | 11:45AM PSTHi Lance,
Thanks for the request for time options with due dates. We don’t currently have this on our near-term roadmap, but might consider adding this in the future.
In the meantime, I would suggest including this information in brackets at the beginning of task titles for visual clarity (see attached screenshot):
[2:00 – 4:00PM] Long walk on the beach.
Let me know if you need anything else.Thanks,
ChrisNOV 11, 2014 | 05:19PM PSTHi Lance,
Thanks for the detailed request for markdown support in Asana.
While we don’t have related changes planned for the near term, we will consider it and note your suggestion.
When we receive a request for a feature that’s not on our current roadmap (usually because we’ve discussed it and decided to save it for later), we label the inquiry so that when we next set priorities or decide to work on that feature, we can easily find customer requests. We prioritize on a number of factors beyond the number of requests (including staffing, cost, overall product goals), but that is certainly valuable information and we appreciate hearing your case.
We appreciate knowing what you think about the product, and your experience as a new user.
As always, you can review existing functionality in the Asana Guide:
Let me know if I can help you with anything else.Thanks,