Time-Off to auto-log hours to the Timesheet - Status changed to: Declined

[#1]

Currently if a user as "Time-Off" booked, they also have to add the hours to their timesheet.

It would be good to (at least optionally) be able to have that amount of time-off auto-logged onto their timesheet. I presume this would require you to pre-categorise the Time-Off Hour Type as Vacation/Sick etc.

[#2]

Yes! We have integrated our proprietary calendar with Time Off via API, but it doesn't talk to the Time Sheet. Its causing such confusion. Need this!

[#3]

100% agree that this should be time sheeted automatically I get asked this constantly by our users!

I also agree its not easy to find....

Thanks

[#4]

Yes, this is one of the problem we are facing. And its weird from the user, that they have to add hours at both places. Because

these kind of small functionality gives a good floe while working in a software like Workfront.

[#5]

I totally agree, and would like to add:

Show bank holidays in Timesheets with a different colour an have this auto-filled accordingly.

The same way - irregular working weekends should be switchable by Sys Admins to "weekday" colour.

[#6]

Hi David and everyone,

We are planning a major redesign of the time management tool in the future. This will be addressed in that redesign.

[#7]

Please make sure you consider Hour Types and Overhead Types when doing this. Right now you when you create a new Hour Type you cannot give it a Scope/Overhead Type of Non-work, only General or Project Specific.

[#8]

Has this been done in the redesign of the time management tool? I don't see my "Time Off" integrated in my Timesheet, yet - in Workfront Classic. Agree that is would be useful to see that in there.

[#9]

Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!

Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.