**As** a user of the app

**I want to** cache my WorkPackage data

**so that** I can see a list of WorkPackages faster

**Acceptance criteria**

Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion when user opens WorkPackages list, he should see them faster Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion **Technical notes**

Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion loading data from server should be implemented with the maximum available page size Begin of the insertion(taken from config data)

* End of the insertion Begin of the deletion
-End of the deletion storing of WorkPackage instances should be done per Begin of the insertionuser.End of the insertion Begin of the deletion user\.End of the deletion In case of switching user, workpackages should persist in database, but shouldn’t be visible for a different user Begin of the insertion

* End of the insertion Begin of the deletion
-End of the deletion an update logic should be based on filter “updated\_at” and on every sync we should sync only a delta between stored time a current time Begin of the insertion

* <br>


End of the insertion Begin of the deletion
-

End of the deletion **Out of scope**

Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion the time of opening a detail of the workpackage won’t change significantly because of two Begin of the insertionreason.End of the insertion Begin of the deletion reason\.End of the deletion First Begin of the insertion-End of the insertion Begin of the deletion \-End of the deletion we’ve already changed the logic of the workpackage so that it shows subject, description, type, status and the project almost immediately from the build Begin of the insertion995.End of the insertion Begin of the deletion 995\.End of the deletion Second Begin of the insertion-End of the insertion Begin of the deletion \-End of the deletion loading activities, relations, files info are separate requests and won’t be included in the first phase of caching Begin of the insertionworkpackages.End of the insertion Begin of the deletion workpackages\.

End of the deletion