Latest updates from the Dubsado team
Bug Fix

Bug fixes Jun 23, 2023

Charis avatar
Shared by Charis • June 23, 2023

🎉 What’s new

Redesigned signup and login page. You probably already noticed a difference when logging in. In addition to a redesign, we added single sign on (SSO) to make your life just a little easier. Read more about SSO.

📍 Roadmap

Watch for new features and submit feedback. We’re happy to share the awesome features we have planned on our roadmap portal! Small disclaimers: Our portal doesn’t cover everything we’re working on, details are subject to change, and features aren’t listed in any specific order.

🩹 Bug fixes

Log out of Dubsado. We fixed the issue where the logout button wasn’t showing if you had a large number of brands.

No save point needed. Duplicating an installment in a payment plan wouldn’t let you save the payment plan. We fixed this, so now payment plans can be saved.

Look at all those clients. If you had a large client list, Projects >> New Project wouldn’t load all your clients. Now, your entire client list will load correctly when creating a new project.

Where do I pay? With Stripe, duplicate payment buttons were appearing on the invoices. This is fixed, so now you’ll only see one set of pay now buttons.

No more mismatched appointments. Sometimes, the “add to calendar” link on an email showed a different appointment time. We fixed this, so adding an appointment to your calendar will always show the correct time.

Resolved Groundhog Day emails. Reminder emails on an invoice’s payment plan defaulted to today’s date. This is no longer the case, so reminder emails will send on the correct date that you choose.

Edit payment plans again. Editing the payment plan used with “after invoice installment paid” in a workflow would remove the payment plan from the workflow. We fixed this, so workflows will either continue normally or you’ll get a warning message.

Fixed duplicate accounts. When logging in with SSO, Google emails with capital letters were creating a duplicate Dubsado account. We fixed this, so SSO is no longer case-sensitive.