Autotask LiveMobile

Every time I change ticket status any more I get a null pointer exception error. This app is useless, it has great potential though. Update, They have fixed the above-mentioned issues and now the app is AMAZING!! Took awhile, but it seems they got most of the bugs ironed out.

I'm really glad we have this app to boost our workflow. Two things: We got into the routine of copying 2FA code before opening the app and signing in. Next, we can't wait to sign in using KaseyaOne instead.

This app was working well but after a recent update it keeps failing after the ticket has been edited. 'NullPointerException' Error Update: App is now working again, and it is brilliant!

I need to be able to add products to do charges on new things while onsite at a job please fix it please and thanks 🙏

Using Sept 10 2021 release on Galaxy S21 (Qualcomm) I rarely write reviews, but having lost data 3 times in one day (and waiting years for this app to become production ready), I've had enough. Summary: Continues to show inadequate requirements gathering and usability testing. Login workflow bugs persist. To any prospective Ditto clients, assume that this is not production ready (or just take heed of the low star count). The good: Resolved previous issue where after entering the MFA key, user would be continuously re-prompted to login again (unless you context switched away from the app). For related issue, please see #3 below. The Bad: More of the same. 1. Android Context Switching results in loss of data: When entering a ticket/note or time entry DO NOT leave the app. While its common in most apps to context switch (ex: to initiate split screen, or to lookup information from an email or text msg), the moment you leave the app or enter "recent app" preview mode, your data is gone and you have to start over. To pre-empt a possible excuse: If local caching is a security concern, the native ACL security models can be enhanced with in-app encryption libraries. If your developers can't handle the state machine and requisite UI workflows, hire better developers. (After 4 years, my patience for this program is long gone). 2. In-App "back" press results in loss of data: When in the Time/Note Entry, if you inadvertently hit the back button, there is no unsaved data warning prompt. The Android API has a BackButtonInterceptor (among other mechanisms) for this purpose. 3. When using an in-screen fingerprint sensor (Galaxy S21 - Qualcomm), the Android OS "finger" prompt does not appear unless the user first presses on a to-be determined part of the screen. After experiencing the data loss issues above (a couple of times), I have not explored the application further to identify other potential "land mines." I come back to this app once a year to see if it has matured to production ready. Over the years it has remained a liability to only use as a last resort, and is not recommended for our internal use. Going on 4 years of needing a mobile app, I'm exasperated. Ditto Staff: No, I will not open a help desk ticket (again). Improve your requirements gathering, QA, and QC processes, and provide an efficient in-app mechanism for submitting bug reports. I have had my fill of repeated "bug reports into the ether" during the pre-Datto acquisition.

The app has gotten better, however in this last release SSO is no longer functioning. AutoTask Come On Dudes??? Still. Latest update is messing up.

App crashes when you click on 'My Tickets'. What's the point of having a mobile app to track onsite time when you can't open a ticket to attach to?