No problem :)

Your suggestion sounds nice.
I was thinking about how to implement a local history to give the user the possibility to revert deletions of stories/backlogs/etc. This would have never been able to be the best solution, because if the user uses more than one device, every device have its own local history.

So if you can deliver deleted ones, that sounds really nice.

How about introducing a new Flag for every object, called "deleted" or something similar.
With a filter argument ("includeDeleted") for that flag (default should be "false" for backward compatibility i think) you could deliver the deleted objects within the same query as you do at the moment.

Josef

That would be OK for me.

>>I am more than happy for you to use the easyBacklog name so long as you state it's not the official app.

So i think i will stick with the name "Unofficial Easybacklog Mobile App" :D

>> BTW. If you need any help with the APIs please shout.

Thanks for your help!

Josef

I think it is useful for the query to get the stories for a theme and for the query to get the acceptance-criterias.

The app is open source and hostet on github.
So it is available for all. But i don't know if i will publish it, on the app market.

Thanks for your fast reply!

Currently i am using synchron requests.

I will change this to asynchron requests today and monitor the API calls' output.

@CURL command

curl -k --user USER_ID:USER_API_KEY https://easybacklog.com/api/accounts/250/backlogs/4702/stats

The time the error occured was: 2013-05-09 23:42:54 [UTC+1]
But i know that i got that kind of error earlier, too.

Perhaps i can solve it by using asynchronous requests. Thanks for this hint!