Hi @Eduardo_Cordoba, welcome to the community!
![]()
Thanks for taking the time to share this detailed use case. At the moment, Asana rules currently rely on task-based triggers, conditions, and fields. They canāt use Time Off data as a native trigger or condition, so overlaps with PTO wonāt automatically notify, reschedule, or adjust dates.
You can approximate this with a workaround:
⢠Use a custom field to track availability or PTO status manually.
⢠Build rules like:
a. Trigger: task assigned or due date set
b. Condition: custom field indicates unavailable
c. Action: add comment, notify PM, or shift dates
⢠Use projects or dashboards to surface tasks by that field.
This requires manual updates or automation since Time Off isnāt directly connected to rules.
A practical workaround is to use a custom field to represent āunavailableā status, then build rules that react when tasks are assigned or due dates are set.
- In the project, go to Customize ā Fields and add a custom field like āAvailabilityā (multi-select works well for āPTOā and āAvailableā).
- Create a rule: When āDue date is setā or āField is changedā ā Check if āAvailability = PTOā ā Do this āAdd a commentā tagging the PM and task owner.
- For reporting, build a dashboard widget that filters tasks by āAvailability = PTOā so PMs can quickly spot impacted work. Another option is using Workload alongside this to visually spot capacity gaps when someone is out.
This wonāt auto-reschedule dates, but it does create a consistent way to flag and report PTO conflicts using rules.
This is a great feature request, and I can see how it would benefit teams managing workloads, capacity, and SLA-driven processes. Thereās already a product feedback topic related to using Time Off data more proactively in workflows, so Iād recommend adding your details and upvoting here: New Rule Condition: Assignee is Out of Office (including My Tasks availability)
Hope that helps! Iām here if you need anything else. ![]()