Email Conversation won't send because tag exists

I think this must be a bug because it doesn’t make sense to me as a feature. I tried to send an email to a Team Conversation and I got an error email back saying other teams or projects exist with the same name. The error email included a link to the team (which I wanted) and a link to a “project” but when I looked up the project ID in Asana, it actually brought me to a tag, not a project.

Why would a tag have an email address associated? This seems like an error to me, and adds another layer of complexity to using email to post Team/Project Conversations – if you now need to be aware of all the tags throughout your organization.

Steps to recreate this issue:

  1. Add a tag to any task
  2. Create a team with the exact same name as the tag you used
  3. Go to the team conversations tab
  4. Copy the email address
  5. Try to send an email
  6. You should get an error that another “team or project” exists with that same name, but the project ID Asana gives you will point you to the tag you used, not a real project

Hi @Justine_D, thanks for reporting this!

Oh, interesting! I was also able to reproduce it on my end. I’ve escalated this issue to our Development Team and I’ll update this thread as soon as I have more information.

Thanks again for taking the time to send us the detailed description and steps to reproduce the issue.

Let me know if you have any follow up questions in the meantime :slight_smile:


Hi @Justine_D, thanks for your patience!

Our Development Team has confirmed that this is actually working as intended. We do allow users to add tasks to a tag via email. So it’s important that the disambiguation logic includes tags.

I understand your confusion here. Tags & projects in Asana work in very much the same way (including creating tasks via email). We recommend you updating the name of the tag or project and add at least one word or symbol different.

Our team will try to clarify the error message to say “tag” instead of “project” in future updates to avoid confusion.

Thanks again for reporting this and sorry again for the any inconvenience!