I'm happy to help people try and figure it out if everyone wants to pitch in with brainpower. (purely an experiment, because I don't know if this is possible or what people have tried)
I took a quick look at the API explorer and I think the collection people are going to want to dig into is called reservedTimes (aka Time Off). If I'm reading this correctly, a single reservedTime has an ID, a start date and an end date, amongst other things.
Best way to see things work is probably experiment in a user report to start with and if you can successfully isolate people having PTO or not having PTO today, you can try and see if that will push into a task report through an exists statement (I'm assuming people only care about the primary assignee having PTO as opposed to multiple users having it).
A sample call in a user report would look like this:
reservedTimes:startDate=$$TODAY
reservedTimes:startDate_Mod=gt
If I'm reading it correctly it will show me everyone who has set a PTO future start date.
To filter PTO-users out, we would want some combination of start date not equal to today, plus end date is not equal to today, plus leave off any occurrence where start date is less than today and end date is greater than today, to cover:
- people taking one day off
- people starting or ending their PTO on this day
- people in the middle of their PTO
So... is that possible, and if so what does the filter look like in a conventional user report?
PS, sometimes it's fun to figure out both scenarios (people having PTO today vs not having) and seeing if one is easier than the other, or if both might be useful in different situations.
