Better link title than "Restore" when queue system is enabled
We have configured jetBackup to use the Queue system.
The problem is that our end-users who did our testing, did not understand this. It is not obvious once the "Restore" link is clicked. They don't understand that they must wait until the queue runs...
Perhaps you could change the link text from "Restore" to "Add to Restore Queue" or something like that? And you could add somewhere in the condition popup that the user understands the Restore will not be instant, but will be added to the queue.. which might take some time to complete, depending on server load, if there's anything else already in the queue, etc..
Also, then please add a link to the queue page, so the user can see the queue easily and monitor status... and on the queue page, maybe also add a box where they can enter their email address to get a notification when queue is completed.
My point is that it is not easy for new customer to understand how everything works. You created the software, so you know what is supposed to happen. A new user, who has never seen jetBackup before... they have no idea... so it is important to help them understand.
All of our test users thought the restore system was broken, because they did not understand that the restore request (and "generate download" request) just goes into the queue and is not instant. So they clicked the link multiple times, and then submitted helpdesk request to complain it was broken and not working…
Jim,
Thank you for the insights, I've created an internal case (738) for our devs about it.
We might need to feedback about it, so I am changing status to "Under consideration", and we will update here accordingly.
Thanks,
Eli.
Jim,
Thank you for the insights, I've created an internal case (738) for our devs about it.
We might need to feedback about it, so I am changing status to "Under consideration", and we will update here accordingly.
Thanks,
Eli.
Hi,
This was implemented in JetBackup 3.3.1
Thanks.
Hi,
This was implemented in JetBackup 3.3.1
Thanks.
Replies have been locked on this page!