I suggest you ...

Notify when data can't be saved.

When an internet connection or server fails, give me SOME indication that data isn't saving.

I've just spent the last 3 hours at a cafe organizing/prioritizing Yodiz for my team. Apparently the internet connection at this cafe required reauthorization after 1 hour. I wish your app had told me I was wasting the last two hours. (!)

Please don't just keep up the appearance of adding items locally in the client; and then when my connection is restored add ONE new item for the last X number of user stories/issue I've create, with a non-deterministic mashup of title and description from items I've worked on in that time.

This lack of visibility to whether or not data is being saved has been around for at least a year, although how it expresses itself has changed slightly since we started using your product 2 years ago.

It's possible this is the same defect as "Make Yodiz save" reported by someone else, which was rejected by Yodiz.

4 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Shannon Massman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
under review  ·  AdminYodiz Support (Product Owner, Yodiz) responded  · 

We are checking the scenario that you have mentioned. We do have the immediate notification in case the internet is completed turned off.
However, in this case it looks like the Authorization was required and we may need to enhance the functionality to cover such cases.

This is always high priority for us to ensure customer data is saved and experience is smooth, we will analyze further and fix this asap.

Best Regards,
Yodiz Support Team

1 comment

Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Shannon Massman commented  ·   ·  Flag as inappropriate

    A minor technical recommendation would be: Use actual proof of save to determine success at the client. For example, look for a response that proves the data was saved, for example a "CREATED AT" HTTP header in a RESTful response, or the created/updated item JSON, the item ID, or even simply "{ success: true }" in the response message. From a web services perspective, it seems unusual that anything other than a real response from the secure destination would be interpreted as success.

Feedback and Knowledge Base