# Tasks Created Via Email Needs Due Date

**URL:** <https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788>\
**Category:** Product Ideas\
**Created:** [14 March 2017 03:03 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788 "2017-03-14T03:03:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Kinney](https://luna1.co/8d76cd.png) [@Michael\_Kinney](https://forum.asana.com/u/Michael_Kinney)\
**Post date:** [14 March 2017 03:03 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/1 "2017-03-14T03:03:23Z")

</div>

Most of our default views are sorted by due date. I often forward emails to Asana to create new tasks, but they do not appear because there is no due date. I have to send the email, go to asana and search for the new task, and add a due date. This is often not possible when I am on the go.

Is it possible to email with a due date? If not, could you make all new tasks default to a due date of today?

---

<div class="post-metadata">

**Author:** ![James\_Carl](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/james_carl/32/904_2.png) [@James\_Carl](https://forum.asana.com/u/James_Carl)\
**Post date:** [14 March 2017 19:13 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/2 "2017-03-14T19:13:08Z")

</div>

Due dates are not available when emailing a task. I know this from my Outlook Add-in, Sendana.

---

<div class="post-metadata">

**Author:** ![Caisha](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/caisha/32/836_2.png) [@Caisha](https://forum.asana.com/u/Caisha)\
**Post date:** [14 March 2017 19:17 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/3 "2017-03-14T19:17:14Z")

</div>

> [@Michael\_Kinney](#):
>
> could you make all new tasks default to a due date of today?

I like this suggestion as a work around for the fact that you can’t add due dates via email.

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/alexis/32/155_2.png) [@Alexis](https://forum.asana.com/u/Alexis)\
**Post date:** [15 March 2017 00:17 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/4 "2017-03-15T00:17:46Z")

</div>

@Michael_Kinney If your default views are by due date, I suggest that you forward emails to your My Tasks rather than a project. From there you can add a due date, a new assignee (if necessary), and use Tab+P to add the task to the necessary project. This [Guide article](https://asana.com/guide/help/email/email-to-asana) shows how you can forward tasks to My Tasks.

---

<div class="post-metadata">

**Author:** ![Michael\_Kinney](https://luna1.co/8d76cd.png) [@Michael\_Kinney](https://forum.asana.com/u/Michael_Kinney)\
**Post date:** [15 March 2017 13:18 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/5 "2017-03-15T13:18:02Z")

</div>

That does not help me. The idea is this: a customer submits a reservation on our website, we get an email from the website with the reservation details, gmail forwards it to Asana, our staff monitors Asana for all tasks including managing reservations.

I am trying to make this automated so I can focus on other things rather then watching for emails.

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/alexis/32/155_2.png) [@Alexis](https://forum.asana.com/u/Alexis)\
**Post date:** [15 March 2017 22:49 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/6 "2017-03-15T22:49:46Z")

</div>

@Michael_Kinney If you’re looking for more automation, then I suggest that you explore Asana’s many [integrations](https://asana.com/apps/). Zapier has pre-built automations. [Tray.io](http://Tray.io) might be able to give you the custom automation you’re looking for.

---

<div class="post-metadata">

**Author:** ![Todd\_Cavanaugh](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/todd_cavanaugh/32/173055_2.png) [@Todd\_Cavanaugh](https://forum.asana.com/u/Todd_Cavanaugh)\
**Post date:** [16 March 2017 06:57 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/7 "2017-03-16T06:57:08Z")

</div>

@Michael_Kinney, this is definitely possible using Zapier. You could set it up so that when you add a Gmail tag to those emails (whether manually or using a Gmail filter) it automatically adds a task to Asana in a specific project with a due date (such as “+3 days” which is 3 days from today). As long as the due dates were consistent, it would be fairly easy to set up. I cover that exact scenario in more detail in the [Asana Training Masterclass](https://projectmanagementpros.com/masterclass/).

---

<div class="post-metadata">

**Author:** ![Valerio\_Romano](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/valerio_romano/32/4147_2.png) [@Valerio\_Romano](https://forum.asana.com/u/Valerio_Romano)\
**Post date:** [15 June 2017 18:45 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/8 "2017-06-15T18:45:05Z")

</div>

Even Todoist has this functionality by simply using [Date 6/17/17] in the body of the email. I don’t use todoist as it is extremely primitive compared to Asana, but I hope this functionality can be implemented.

---

<div class="post-metadata">

**Author:** ![James\_Carl](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/james_carl/32/904_2.png) [@James\_Carl](https://forum.asana.com/u/James_Carl)\
**Post date:** [16 June 2017 01:28 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/9 "2017-06-16T01:28:33Z")

</div>

The real solution is for me to continue the work on G-Mail version of Sendana, [www.sendana.net](http://www.sendana.net) .

 ![](https://us1.discourse-cdn.com/asana/original/2X/6/651fe1b22a68e75d75a4d9267884db598c9124cb.png) so all you non-Outlook users don’t feel discriminated against. PC users that use G-Mail can simply buy Outlook and use its automatic sync. Believe me I know about every field that can be emailed or has to use the API because we had to address all of them and how to have Sendana look them up. Next week, we work on Tags. 🙂 When I complete the G-mail project I assume the MAC users will be happy also.

---

<div class="post-metadata">

**Author:** ![Tyro](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/tyro/32/3352_2.png) [@Tyro](https://forum.asana.com/u/Tyro)\
**Post date:** [18 June 2017 19:54 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/10 "2017-06-18T19:54:32Z")

</div>

@James_Carl Looks very cool! As a gmail user - looking forward to seeing this!

---

<div class="post-metadata">

**Author:** ![James\_Carl](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/james_carl/32/904_2.png) [@James\_Carl](https://forum.asana.com/u/James_Carl)\
**Post date:** [20 June 2017 18:47 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/11 "2017-06-20T18:47:40Z")

</div>

It is in the works. Unfortunately it is our policy to not promise any estimated time of release but know that it is in the pipeline 🙂

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/alexis/32/155_2.png) [@Alexis](https://forum.asana.com/u/Alexis)\
**Post date:** [20 June 2017 19:17 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/12 "2017-06-20T19:17:43Z")

</div>

Sounds familiar 😜😁

---

<div class="post-metadata">

**Author:** ![James\_Carl](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/james_carl/32/904_2.png) [@James\_Carl](https://forum.asana.com/u/James_Carl)\
**Post date:** [20 June 2017 19:26 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/13 "2017-06-20T19:26:20Z")

</div>

I thought you would like that and know you have a great sense of humor 🙂

---

<div class="post-metadata">

**Author:** ![Tyro](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/tyro/32/3352_2.png) [@Tyro](https://forum.asana.com/u/Tyro)\
**Post date:** [20 June 2017 22:57 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/14 "2017-06-20T22:57:46Z")

</div>

@Alexis One big difference though: @James_Carl **told us it’s in the pipeline!** So far, asana will not even take that step. (I know, I’m ruining the moment I’m sorry 😈 - but this is really important to my business so I keep harping on it).

**A good compromise would be** [what Spotify does](https://community.spotify.com/t5/Newcomers-and-Contribution/The-Ideas-Board-How-your-feedback-reaches-Spotify/td-p/896827): at least [let us know when a feature or fix is completely off the table for the foreseeable future](https://community.spotify.com/t5/Newcomers-and-Contribution/The-Ideas-Board-How-your-feedback-reaches-Spotify/td-p/896827).

> The Community team talks with various other Spotify teams several times a month about the ideas that have over 100 kudos. It’s from these meetings that we apply one of the following statuses to each idea:
> 
> **Good Idea, Give It Some Kudos** - We like this idea. A decision has not been made but we want to see how much the Community continues to vote on it.  
> **Not Right Now** - We talked about this internally and it’s not on our timeline for the next few months or more.  
> **Under Consideration** - This has been brought up internally.  
> **Watch This Space** - This feature is coming. We have a rough timeline for its release.  
> **Implemented** - This feature has rolled out.

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/alexis/32/155_2.png) [@Alexis](https://forum.asana.com/u/Alexis)\
**Post date:** [21 June 2017 17:46 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/15 "2017-06-21T17:46:57Z")

</div>

We hear your suggestion, @Tyro. As I’m sure you can understand a lot of people are involved in the decision to reveal or to not reveal a product roadmap publicly. As your community manager, I have delivered your feedback to my team 😇 and they’re aware of your feedback.

---

<div class="post-metadata">

**Author:** ![Tyro](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/tyro/32/3352_2.png) [@Tyro](https://forum.asana.com/u/Tyro)\
**Post date:** [21 June 2017 18:28 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/16 "2017-06-21T18:28:00Z")

</div>

Thanks, @Alexis! I do appreciate it.

---

<div class="post-metadata">

**Author:** ![Jean-Christophe\_Lavo](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jean-christophe_lavo/32/4385_2.png) [@Jean-Christophe\_Lavo](https://forum.asana.com/u/Jean-Christophe_Lavo)\
**Post date:** [26 June 2017 18:57 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/17 "2017-06-26T18:57:25Z")

</div>

> simply using [Date 6/17/17]

This would be a great implementation.

---

<div class="post-metadata">

**Author:** ![Rebecca\_Fiebrink](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/rebecca_fiebrink/32/5537_2.png) [@Rebecca\_Fiebrink](https://forum.asana.com/u/Rebecca_Fiebrink)\
**Post date:** [29 August 2017 10:19 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/18 "2017-08-29T10:19:46Z")

</div>

This is my highest-priority need from Asana right now. My organisation doesn’t use gmail, so I can’t use Zapier. At the very least, I would appreciate the ability to do a search within Asana for tasks that do not have a due date, so that I can manually add due dates to tasks from email.

I will most likely stop using Asana soon due to lack of this feature, as manually creating tasks that correspond to email is taking too much of my time.

---

<div class="post-metadata">

**Author:** ![Caisha](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/caisha/32/836_2.png) [@Caisha](https://forum.asana.com/u/Caisha)\
**Post date:** [29 August 2017 21:15 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/19 "2017-08-29T21:15:51Z")

</div>

> [@Rebecca\_Fiebrink](#):
>
> manually creating tasks that correspond to email is taking too much of my time.

Hey @Rebecca_Fiebrink, regardless of what email client you use, you should still be able to email Asana tasks and forward them, etc. Sorry if you already knew this and you just mean assigning due dates is taking too much of your time.

You could always just add the due date in as the first line when you email tasks? None of it’s ideal, I want this fixed too, but that way whomever gets your task can assign the due date on their own, etc. And when you go through your My Tasks every morning (or whatever), you can arrange your day and add due dates while you do it.

---

<div class="post-metadata">

**Author:** ![Michael\_Kinney](https://luna1.co/8d76cd.png) [@Michael\_Kinney](https://forum.asana.com/u/Michael_Kinney)\
**Post date:** [29 August 2017 21:47 UTC](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788/20 "2017-08-29T21:47:52Z")

</div>

The problem we only use tasks sorted by due date and therefore don’t show up. If they could default to today that would work as well

[Next page](https://forum.asana.com/t/tasks-created-via-email-needs-due-date/788.md?page=2)
