Thanks for the feedback Andrea,
The suggested workaround of using custom fields could do for the time being, but I’d really like to leave this post unsolved (and with the ability to be voted on) to see how much interest there is in properly developing this feature.
Fake e-mails won’t work as we work with up to three dozen external parties on any given project, across many dozens projects with unique parties. This is common in consulting engineering (buildings / infrastructure). Making that many unique fake e-mails just to get around a missing feature would negatively impact our work flow.
Custom Fields will bring some of the needed functionality, but it doesn’t show in the Gantt Chart view which is how we primarily organize ourselves in Asana. It also doesn’t auto fill external parties who have already been entered into Asana once (like how the assign feature shows and searches the people in your team) which can lead to misspelling, non-consistent naming, and in general inaccuracies.
Our external parties are not working within Asana directly, but we do need to be able to visualize in Gantt Chart view which of them is responsible for what. If we want them to work on the task directly we can add them as a Guest, that’s fine. However if we start hounding our clients (governments, large developers, architects) to start using Asana via e-mail notification when we work with them they’re most likely to see this as something they didn’t ask for and be upset (they value their time and inbox cleanliness). We would be jeopardizing the likelihood of getting to work with them in the future which is not an acceptable result of our use of Asana.
Can you please return the ability for this post to be voted on as I’d like Asana to consider implementing this feature.