Phil, agreed, and I am not trying to be obnoxious. But I am doing a thorough analysis of Asana, and I intend to be discerning as there is a ton of investment and opportunity cost when you commit a team to a Work Management tool. I too am an entrepreneur and software creator, and it goes against all Agile/Lean and general best practices Iām aware of to ignore customers to this extent. There really should be no threads in this forum - which is heavily promoted by the Asana Product Team themselves - that are ignored. At the very least I think there should be enough staff assigned to the forum to provide transparent communication, so the frequent voices of āstop ignoring usā disappear. We are talking about an organization with massive means: pre-IPO, large engineering team, etc. They are at the top of its industry:
So I am coming in with high expectations. And facing $30/month for a license (I canāt do yearly, and need the business features), plus probably double that for plugins that offer basic functionality absent, like time tracking, Gantt, your excellent tool, and adding Custom IDās (!), this is all the more reason my expectations are high.
If you look at that chart and the mass of tools coming up on Asana, many of which Iāve extensively tested, none have:
any issue with whether you can view your project in a list or board - took forever to get that fixed here
the notion of a āstart dateā on a task - also took forever to implement
Asana is fairly brilliantly conceived with itās structure and flexibility. But this is not stuff thatās particular genius, and many of the tools on that chart mirror the basic functionality of Multi-homing tasks. On the other hand, more of the basics that are missing in Asana around the great structure, like this list above, are coming along slowly in my opinion, compared to the other guys who are more agile as I observe the way the listen to user requests.
I appreciate that Asana is now at scale and no work is easy. But that comes with being successful. Itās a very competitive space, and some of these features have to be added, no matter how challenging, or users will look elsewhere.
Unfortunately this is not useful as those numbers show the order and are not related to the task. So if you change their places task that was number 2 will become 1, etc. You cannot reference to those numbers as unique identifiers.
Right, I understand that row numbers can change with the addition of tasks and reordering. I offered that workaround thinking of a real time phone conversation where both people have the project open and someone might say āTask number 12 under Planning.ā Beyond that, I agree it is not particularly useful. Thatās why I also referenced the copy task link.
I completely agree tasks should have visible Unique IDsā¦really everything should for ease of reference.
Currently, when viewing a list of Projects, the Project List shows the Team Name in smaller text underneath the Project Title. It would be great if this could show the number of tasks within the Project.
Example:
Welcome to the Forum @Nathan_Goss and thank you for sharing your feedback with us!
This is a popular request in the forum and we currently have a thread regarding this topic so Iāve gone ahead and merged your post with it for consolidation purposes. I hope itās OK
Thank you again for your feedback! Have a great weekend!
@Natalia - Iāve read SO many requests for this feature. Is this on the product roadmap? Is there a public Asana roadmap? Iām sure youād have tons of people whoād be glad to give you feedback in an Early Access Program if you wanted : )
I agree with Mark (and MANY, MANY more). This topic/feature request has been around for a LONG time, but there is no feedback from Asana. Is this even a consideration for Asana?
I just got an invitation to an āAsk us anythingā event from the EMEA Customer Success Team. I presume a few others here did too. I might try and join so I can ask them about this.
The issue @Nathan_Goss has is not the same as the one being discussed in this thread. However, while we have you, could you try to get some answers for the customers who have been asking questions on this thread for a long time?
I was reading through the topic again, as my only real concern before going paid with Asana was this misfeature. Years passed, we are paying, but I still donāt see understanding or will to change from the Asana team. Iād like to see they understand the issue.
Let me describe 2 scenarios:
Developers has to refer a bug or feature ID in their git commit messages. Word and character count really do matter in commit messages, writing āPROJ1#123ā is much shorter than copy-pasted urls. Before Asana we had a strict system requiring to prefix commit messages with task IDs.
Donāt come again with the task numbering, that would mean we canāt insert new lines into task lists, only append to the bottom, but there is no such limitation in Asana UI so thatās not a real solution, and Asana team is bringing this up to silence people on the forum about this.
Linking tasks for client project reporting. URLs are super ugly, seriously. No chance we put those into an email or official document. On Asanaās UI itās nice that in rich text fields the URL is substituted by the task name. So copying and pasting url into a temporary field end than copying the URL from there into the report would be a solution, but the link text doesnāt include the project, only the task name. No joy here either.
This has impacted our internal processes, code quality, project management.
I have seen other companies stepping in and trying to solve the issue with plugins, but any tech leader will try to limit 3rd party access. Is our only option to switch to Jira?
Hi @Natalia As I read Nathanās post, itās clear when he says ānumberā of tasks, he means the total quantity of tasks, not an ID number. So as @Liam_Ward says, Nathanās post does not belong in this thread.
