To support the offline work and reduce the volume of downloads from the server, Deskzilla works with the local database and all the information available in Deskzilla is taken from it. To ensure the information in the local database is always up-to-date and has all the recent changes made in Bugzilla, Deskzilla regularly sends a request to the server to get the change log and if necessary downloads all the recent changes. By default this synchronization is ran runs every 150 seconds (if there is a server connection). Synchronization runs in the background and since the updates are done regularly the amount of downloaded information is usually small and does not affect application performance. You can also run synchronization manually by clicking the Get Changes Now button 
on the application toolbar or pressing F5.
| Tip |
|---|
When adding a new connection select only the products you are going to work with. This will reduce the local database size and time required for its update. |
Loading configuration
When a new connection is added Deskzilla downloads its configuration (version, workflow, products, components, etc). Every 12 hours Deskzilla automatically checks for configuration updates and if there are any changes, reloads configuration from the server.
You may need to reload configuration manually. For example, you know that the configuration was changed and you need to work with those changes (for example, a new version of the product was added). To reload Bugzilla configuration, select the connection to update and select Reload Configuration from the Connection menu or press CTRL + F5. This will download both configuration updates and bugs changes.
Queries synchronization
When a new connections is created all its queries are unsynchronized. When a query is ran for the first time Deskzilla runs it on the Bugzilla server and retrieves all the bugs the query contains from the server. After this is done a blue label next to the query will show the number of bugs it contains 
. Naturally, all sub-queries of the synchronized query are also synchronized.
| Tip |
|---|
It is recommended to run the All Bugs query when a new connection is added. It will take some time, but since it is the root query and contains all the bugs, once the process is finished all other queries will be synchronized as well and from that moment you will work with the local database only, which Deskzilla will keep continuously up-to-date. |
If at some point Deskzilla detects that the query may not be up-to-date, the blue label with the number of bugs is removed. If you run the query in this situation Deskzilla will first show the bugs based on the local database data and run the update process in the background.
If a connection is modified all its bugs and queries should be synchronized again, because the change of the user, for example, may affect the query results.
| Tip |
|---|
You can also view the query results in the browser. To do that, right-click the query and select Open Query in a Browser. Please note, that for technical reasons this function may return more bugs in the browser than there are in the query. |
Bug details download
When running an unsynchronized query for the first time Deskzilla downloads most of the bug details, however some of them are downloaded later, when you open a bug details. This is reflected in the bug info bar at the bottom of the bug details area 
.
To download all details for a set of bugs, select these bugs in the bug table, right-click them and select Download All Details or press SHIFT + F5.
If bug details were downloaded before, but you want to make sure the bugs you are viewing have all the latest updates, select and right-click them and select Reload All Details or press SHIFT + F5.
Status bar at the bottom of the page shows the number of bugs in the local database and the synchronization status 
.