If you've ever made a group booking and selected the wrong leave type, dates, or department then you'll know that deleting them as individual bookings can be a painful experience.

We think so too. So we fixed it. 🙌

Admins (and only Admins) can now delete group bookings in a couple of clicks just like any other cancellation:

You'll get a summary email detailing who the cancellation affected and the users will all get an email to say it's been cancelled too.

This will only affect group booking made from now - we don't have the data on older group bookings to link them together as one.

If you're an API user you'll see bookings now have a "GroupID" field - this is how you can tell if a booking is part of a group (from today).

Hi there 👋

We’ve made a small update to how carry forward works in Timetastic — just to make things clearer and more accurate.

Until now, you could choose to have carried-over leave expire after 1–12 months. But behind the scenes, setting 12 months actually meant the leave never really expired.

To make that clearer, we’ve introduced a new option - Carry forward never expires

You can set carry forward to expire after any period between 1 and 12 months as before, or choose “Never” if you don’t want it to expire.

Anyone currently with a 12 month expiry will be switched to have "Never" expire to match how the old feature worked. But if you'd prefer an expiry on carry forward? You can still set 1–12 months by going to your carry forward settings.

We've also given some TLC to the calendar summary page to make it clearer how much carry forward is available at any point:

If you are in the carry forward period you might see the following, letting you know how much carry forward you have, and when it needs to be used by:

After the carry forward period you might see this, indicating any carry forward that was not used:

We're updating the help centre with more details on this.

Thanks to one of our API users reaching out with a bug on the absence endpoint. GET requests with parameters in the query string (as you'd expect) should work fine now. Huge apologies for this, we should have caught it and we're improving our API test suite as a result.

We're also updating some backend security things as we do from time to time, you shouldn't notice anything different here though.

We've just pushed out a couple of fixes:

A fix for the wallchart filter which we had reported. Users who are approvers of people in other departments can now see those users on the wallchart. (regardless of privacy settings, as they're approvers).

Changing price plans (Business to Pro or back again) now reflects in your audit log.

We've got more on the way. Stay tuned!

Hot on the heels of monthly reporting, today we've sorted an issue where times for half days were incorrect in the absences API endpoint. 

We've also rolled up a fix to the "What's new" widget in the footer so it works now.

Yes, you read that right. Monthly reporting is here which should explain why our reports have been seeing some adjustments and tweaks lately 😁.

It's probably our most requested feature and we've been working away on this for a while now, so I'm really happy to be able to share it with you all.

You can now, finally, find out how many days off were taken in a specific month. Either by a user or by a specific leave type. If the booking crosses over multiple months that's fine, you'll get the numbers for the month you requested.  You'll see a brand new monthly report in Settings > Reporting & Backup which follows our usual reporting format.

Data is available for all of your bookings as far back as the start of your user's current leave year and all future bookings from now on and this is available for everyone on all Timetastic plans - we're not making this Pro only.

We're updating the help centre with more details on reporting in the coming days with full explanations but hopefully this will make your lives easier.

You'll notice we've renamed and moved some columns in the reports on the Leave sheets - apologies if this breaks your macros/integrations but it's for good reason, we promise.

We've collected up some bugfixes around allowances being recalculated wrongly if they finish at midnight and some speed improvements to reporting and allowance calculations.

Small update that hopefully improves your reporting a bit - we've added booking ID to "leave" sheets in reports and added a user's department name too. 

Keep an eye out for future reporting updates!

We've had this one requested by a few people and it's always been a good idea. So today we're solving a pain point with the API. 

Who is absent on x day?

Previously you'd need to query the bank holidays, work schedules, holidays endpoint for every user to get a nice list of who is off. Then merge them all together at your side. 😱

Now?

Just query api/absences with your dates and what type of absences you want and you'll get a list broken down by day and by user with everyone's absences. 👌

You can query for just public holidays, bookings, all types of absence (public holidays, non working days, bookings) or if you've got an external dashboard/app to update and want to get everything you see on the wallchart  then query "AllEvents" and you'll get work anniversaries, birthdays, locked dates and all absences. We include some basic data and the associated record ID so you can query for more data if you need it.

We limit the endpoint to 31 days so you can query for a whole month at a time and we've had to rate limit this to 1 request per second.

Full details are in our API docs: https://app.timetastic.co.uk/api-docs/index.html 

Show us your integrations - we'd be keen to see how this is being used! https://x.com/timetastic 

Small but important update today. We've updated and moved the API docs 🔧. There are no changes to the underlying API so you can rest easy, but the postman collection has now been replaced with a nice OpenAPI specification document.

https://app.timetastic.co.uk/api-docs/

We'll be improving these over the coming months so if you spot anything wrong/missing let us know.

All your old links to API docs should still work and any future updates will be made to the OpenAPI spec rather than the postman collection.