All Collections
Product updates
2020
June 2020 Release notes
June 2020 Release notes
Patrick Gruhn avatar
Written by Patrick Gruhn
Updated over a week ago

Over the last 12 months, we've been working hard to improve your experience when using Planday, both on the web and your mobile devices.

This month, we've completed a significant step in making Planday fit for your every need, by:

  • improving the general stability of the platform (fewer access issues and timeouts)

  • decreasing loading times (up to 3+ times faster in some cases)

  • ensuring the long-term sustainability of our platform (setting the stage for many more features!)

As we're monitoring closely (and fine-tuning) the results of a year's worth of intense and active effort, there are no new features for this month.

We'll make up for that shortly because a lot is coming up in August!

Mobile

Make sure to use the latest versions available for Android (6.6.0) or iOS (6.6.1).

With the newest update for the Planday App, we:

  • fixed an issue that caused the app to crash when signing up for a new account

  • ensured the Punch Clock reminder for a shift ending soon triggers at the correct time.

  • fixed a bug that prevented worked Hours ( per Employee) to be displayed correctly in the Schedule view.

  • added translation fixes for German

  • fixed a bug that prevented periods marked as Unavailable appearing in red, under Account > Availability

  • improved usability for the Request widget, ensuring that the See all button is visible, when relevant.

  • ensured that the Schedule data loads and is shown correctly.

  • fixed an issue causing Shift times to be displayed wrongly, if not set when the Shift was created.

  • added translation fixes for German


ℹ️ Need more help?

🔍 Search the Help Center | See videos at Tutorials.Planday.com | Watch a webinar

💬 For personalised support

Login and contact our support team via the blue icon at the bottom if you have more questions or book a one-to-one professional training session with an expert.

Did this answer your question?