Hey Bastien,
Thanks for the reply. You’re right in that I was informed by the Asana Support team that using these custom date fields is not currently accessible to be reported on in the dashboard.
You’re saying that instead of a date field, create sub-tasks as “touch fields” and then use those subtask completion dates as what I could filter instead?
Yes, you can create a subtask through a rule with today’s date, maybe that’s a good way…
It would be extremely useful to my organization to be able to write rules around custom date fields.
We often receive information about the expected due dates of a larger business goal via a custom date field in our form, and would like to be able to use that information to set the new task’s Due Date x number of business days or y number of weeks prior to that date. It would also be useful to be able to generate comments, move tasks between sections, or set status fields alerting people to risks associated with goal dates that are not far enough in the future.
The “update task” category in rule actions has very limited options.
What I would like to see is an action that allows updating a custom date field with the date at which the action is run.
It would also be great if this was more general, ie, being able to update any custom field, not only the current set of standard fields.
I hope (and believe) those are definitely coming. In your case we’ll need two things: ability to update other types + Custom Variables in Rules to be able to pick the rule run date.
@anon56345047 (and others here),
FYI we just added support for date custom fields in our Flowsana rules.
+1 for this feature! Custom date Fields have existed for a while now, so it’s surprising that these are still not available when setting rules. Asana, please enable Custom date Field Rules!
It is indeed a late fast-follow we are expecting!
Do you know if Asana has created that trigger / action yet? Or if there’s a work around to make that happen?
Hi, I think this has been mentioned in a previous post from nearly a year ago, but it would be very helpful when creating custom rules if Custom Due dates were to be added. For instance, if there are three due dates attached to one task ( and the additional dates aren’t suitable to be listed as subtasks alone), it would be helpful for one of the three due dates (not the main due date) to act as a trigger for a rule. I hope this would be helpful to others as well! Thank you!
Like many others have mentioned here, it would be good to extend the Triggers in the Rules so that we can leverage the new custom date fields that are provided. At the minute we’re using Due Date as that’s the only date field that allows a trigger, which is causing a few issues on our end.
Well, you can use our Flowsana integration, which has both triggers and actions based around custom date fields. 
Hi there. I’m hoping someone can help me out with the custom date field format Asana requires. I set up a zap to go from my CRM to Asana (date transferred) and used the date formatter Zapier provides. I’ve tried numerous different date formats and nothing seems to transfer to asana. Any help would be appreciated!
Thanks.
Agreed with Joe6’s comment. We’re in a situation where we have a custom date field that we need to set when the task hits a specific stage in production. Currently it looks like we have to do it manually, but I really wish it would work with Rules. I know we can use the rules to manipulate the task Due Date, so I hope it’s not much of a stretch to alter custom date fields too.
@SamW, if you are able to use our Flowsana integration, it’s easy with our “Set a date field” rule action:
This feature is desperately needed in order to leverage reporting (in terms of high-level communication on the status of sets of projects, not the reporting features) to its fullest. Our current use case is the need to run reports on how long it has been between a document request being submitted and now or when the document is received. Since there is no way to write rules for specific subtasks, this is currently a very manual step, either setting a custom date field by hand when checking of the “make request” subtask, or going back after the fact and digging through the history to find out when the subtask was completed. It would be completely automated if a rule could set a custom date field o today’s date when the entire task’s status is changed to “request submitted”
And yes, I’m aware that Flowsana has this capability, however, my organization does not support the use of Flowsana at this time, and a native solution is needed for this very basic function of reporting how many days have elapsed between subtasks.
Anyone figure out how to trigger or set a date when a custom field is changed? Looking for a way to show testing statuses and how they change statuses over the course of UAT. Was thinking maybe to use a rule to update the custom date field when testing status changes, but I cannot seem to figure out a rule that i can use.
You can’t set a date field yet, this action doesn’t exist. And in terms of trigger, “field changed” doesn’t it, you only have “field changed to X”. Does it help clarify?
Thanks. This would be greatly appreciated.
