Here is the trick of the day!
Custom fields of type Date don’t exist yet, so usually people use a text field to store some date on a task (that is not the due date).
If you want to be able to sort the task list based on that field, make sure to input dates in YYYY-MM-DD format. That way, an alphabetical sort will actually be a chronological order!
Pretty cool right?
Do you know if there is a way to do a multi-tier sort? We have a project with tasks set up with multiple custom fields. We can do a primary sort using one of the custom fields. However, we need a secondary sort with another custom field.
Example… custom field 1 is customer and custom field 2 is project. We want to sort all tasks by customer and then by project (or the reverse… by project, by customer).
I cannot find a way to do this in Asana. Can you point me in the right direction?
That is correct, @Bastien_Siebman. Currently, you are only able to perform a single condition sort.
The only other delineation is you can filter by a separate custom field or utilize sections to separate tasks by a specific criteria.
Here is the #productfeedback to upvote the suggestion to perform a sort across multiple conditions: Sort project by 2 criteria (Due date and assignee for example)
@Michael_Hess, For a workaround, consider:
@Bastien_Siebman, if you want to use this for your 🔥 Hottest feature requests and their workarounds do feel free!
Larry
This is a great suggestion. . . . any idea when (or if) we’ll be able to create a custom field that’s a date type?? I have to do this a LOT - e.g. for test start date or go-live date & don’t want to create lots of additional tasks, just want a nice way to keep track of the information & would like to do less typing.
PLUS, I work with a lot of international people who don’t love US date formats, so I have to do lots more typing to add month. Would love to pull off a calendar & then everyone can see it the way they’re used to.
My gut feeling says it will be available one day, but I have no idea when. The problem with this type is that it could encourage people not to use the Due Date but a custom field instead, and that might confuse some of the new users. So maybe the Product team is hesitant 
#guess