Hello everyone!

It's a mobile update release. ☎️ 🤙

Looks like we've had some issues with the mobile app recently - specifically things like the login link, and resetting passwords haven't been behaving properly.

This release sorts all that. Best of all it's a server-side fix so no-one needs to go and update their app - hooray!

Improvement 

The user uploader wasn't great at telling you why your upload might have failed, so we've improved it to be better at handling different date formats in CSV uploads and telling you more about what could be wrong (or right) about your upload.  

Fix 

The reports change last week introduced some unnecessary fields on some report sheets. We've sorted that out so only relevant fields are shown now. Apologies if you've just adjusted your macros!

There's some more improvements, fixes and tweaks as with all of our releases too.

Improvement 

The Summary and Backup reports now have a standardised column layout for users so you can now reference them by ID, payroll ID, and their first and surnames. 📊

Payroll ID?

Yes, as some of you will be aware, we're beta testing a Timetastic Pro plan and Payroll ID is one of the new fields you can add to a user if you're on the Pro plan. We'll be reaching out to more companies to test our Pro plan before we launch it properly in the future. So keep an eye out for that, there's some really good stuff in it. 👌

Fix 

We fixed the issues saving Webhook URLs and a few other issues on the Webhooks API page.  🐛🔨

Security announcement today 🔐 

We've received Certificate of Assurance that we meet the Cyber Essentials Scheme requirements 👏 

Nothing too exciting here, but we’ve wrapped up a suite of fixes improvements and tweaks in the background. 🛠

More exciting things to follow, we promise 😀

It’s Friday! Let’s throw another release at you!

We’ve been fixing some minor niggles and issues - here’s some more detail!

• 📅 We fixed an issue where if you were in a user’s profile from the calendar page you wouldn’t be offered a pro rata for that user when adding a start date. Now you are.
• 💳 We had some payment setup flows that could in rare situations leave you unable to enter card details, these are all sorted now.
• 🪵 We made some improvements to our new sign in logs
• 🔤 We found and fixed some smelling mitsakes ;)

That’s all for now, get back to it, and we’ll see you again soon.

👋

New, nouveau, neu, nuevo - security page and sign-in flow.

Following hot 🔥 on the heels 👠 of last week’s release, today we introduce some changes related to how you sign in to Timetastic. 🔐

You’ll notice, when you’re next prompted to sign in, that we’ve spruced up the look-and-feel of the sign-in process. The changes are not entirely aesthetic though: we’re splitting entry of email address and password in order to pave the way for additional options in future (🤫).

Finally, we’re recording user sign-ins so that we can give your admins the means to view this information for your organisation. They’ll find it on a new Security page, under Settings.

Say hello 👋 to “Recent Transactions” our new addition to the reporting and backup page. 📊

As an Admin user, you can now see a list of recent leave events (bookings, approvals, cancellations etc.) and download it from the same page you normally get your reports.

To fit recent transactions in, we’ve redesigned the reporting page to make it a bit more organised and clean.

Also we fixed a really edge case bug on rendering public holidays on the Wallchart 🛠

That’s it for now, stay tuned for more!

A couple of small improvements today:

• We’ve tweaked the way we load user profile photos as, in some circumstances, we were inadvertently trying to load non-existent images.
• We’ve upgraded a client library to ensure that we’re keeping up to date with maintenance releases by our platform providers (ever seen the film “Inception”? 🕶 ).

Happy Monday! Couple of small things today..

Security 🔐 - This release sees a limit on the number of login attempts you’re allowed before your account is locked for a while.

Back End Stuff - We’ve fixed a couple of back end niggles and issues, to keep things running ship-shape 🛳

That’s all for now. 👋