This is important for professional project management software. The timeline view is about 8 days off per month across the entire team just by having weekends counted as working days. If I have 10 people on my project, that’s about 80 days of budgeted time out in a single month. This impacts both the delivery schedule AND project budget in a big way. For large projects spanning months, most PMs are trying to build a schedule out with nothing more than a task name, duration estimate, and dependencies. The ideal scenario for using the timeline view to visually plan is the PM sets the duration of a task, which sizes it, then move it around with Asana auto-scheduling the start and end date based on the estimated duration and where the PM drops it.
+1
Such a basic feature tbh
+1
FYI we just added a new rule trigger condition in our Flowsana integration that lets you identify when a task gets scheduled on a holiday or user’s time-off:
Is there any update to this feature? We have team members who work 2-4 days a week on a set schedule but cannot update their workload days. Needed feature for organizations who don’t have 5 day work weeks.
any news on this feature?
I would really like to be able to block out holidays and vacation times for co-workers and managers. With so many users requesting this, it’s hard to believe it still hasn’t been added as a feature.
Hi everyone! Here are some updates on the various asks included in this post (I also marked this as “Considered”):
- First: Work Schedules on Projects had previously shipped, but it exists as a project setting. It’s leveraged to inform dependency shifting and calculate SLAs for use cases such as ticketing. We don’t yet support user level work schedules.
- Coming over the next few months will be a number of out of office (OOO) improvements, including the ability to set multiple out of office periods vs the current single out of office setting.
- Support for multiple OOO entries is a prerequisite for supporting the ability to set holidays that would inform dependencies, workload etc… it’s still a bit early though for me to share a timeline estimate though.
That’s great to hear, @Garrett_Knoll. Has scheduling based on an individual’s work hours been discussed as a potential future part of this initiative? My company has several overseas offices, and many of the projects I administer would benefit from being able to auto adjust due dates based on the assignee’s working hours vs the project’s working hours. “X days from trigger” can be a much shorter functional time frame for non-US reviewers. Say I trigger the creation of an assigned subtask on Wednesday in the US, but in this particular task, the appropriate assignee is in Australia. For them, the due date falls on a Saturday. It would be great if I didn’t have to account for this with a separate rule action to set an appropriate due date based on the specific assignee or country.
@Leigh_Flynn So “Work Schedule” (days of the week people work) is at the Project level. This can also be accounted for in Rules. But I do advocate for us to better surface the time zone and due date / time of a Task when a user assigns someone a Task. Asana is a global company and I personally feel this pain point myself. It’s in our backlog to improve this!
Awesome!
On a related note: Enable setting a work schedule in project templates