Deskzilla lets you search, view, modify and create bugs even when you are offline, when Bugzilla is not reachable, or when you have a slow VPN connection.

This is possible thanks to the local database of downloaded bugs maintained by Deskzilla. You change the local copy of a bug and Deskzilla tries to upload the change when possible. In case of a conflict with changes done on the server, Deskzilla helps you to merge conflicting changes.

To keep the local database up to date, Deskzilla periodically checks the server for recent changes.

In Deskzilla, queries are the starting point for working with bugs. A query filters bugs and displays a tab with the results.

If a query is placed under another query, it will filter the results of its parent query. By constructing a hierarchy of queries, you can organize a large number of bugs into a manageable structure.

Once you run a query, Deskzilla will keep it synchronized making sure you have the bugs that it returns in your local database. For synchronized queries Deskzilla also shows the number of bugs that satisfy this query. This provides you with a quick overview of the current state of the bugs.

If you are working with several Bugzilla servers, you can add a connection to each of them in Deskzilla and have all the data you need in one place.

A distribution groups bugs by a selected field. Essentially, a distribution is a number of sub-queries, where each sub-query shows only the bugs with a specific value in the field.

You can create distributions by Status, Assignee, Priority and other fields. This lets you quickly get to the bugs you're interested in, while preserving context in the navigation tree.

Another type of distribution, 2D Distribution, can group bugs by two (or even more) fields.

2D distribution table can be opened under the navigation area or in a separate window.

If you drag a bug from a table and drop it on a query in the navigation area, Deskzilla will try to change the bug so that it satisfies the query's filter.

You can think of it as if you're actually moving the bugs into a "folder", represented by the query. Some queries (like filtering by date or by text) don't support this kind of change, but most queries will let you change one or more bugs just by using drag and drop.

If you do a lot of triage or need to assign many bugs to different users, you can set up a number of queries that represent your typical changes and then just drop the bugs on them.

Deskzilla offers multiple ways to find bugs you are interested in. One of the quickest is the context-based text search.

Select the query that will limit your search scope and type a word or phrase to search for in the search field at the top of the main window. Deskzilla will return the bugs that have the specified words and that satisfy the query you have selected.

Select the bug you're working on and click Start to begin tracking the time. When done, click Stop or switch to another bug. Deskzilla will measure the exact time you've spent on each bug.

Later, you can review the time sheet, make corrections and publish tracked time to Deskzilla.

Optionally, Deskzilla can detect the periods when you don't use your computer and automatically pause time tracking.

With a screenshot tool you can quickly add a screenshot to a bug. If necessary, you can also use the screenshot editor for zooming into details, blurring sensitive information, adding your comments or highlighting certain areas.

Create personal tags and apply them to selected bugs. To see the bugs that are tagged with a certain tag, you can simply double-click this tag in the navigation area.

Tags are saved locally and are not visible to other users, so you can use them to create your personal bugs collections.

Select multiple bugs in Deskzilla and use Copy to place the bugs into system clipboard. (Hit Ctrl+C, or Command+C on a Mac.) Then, you can use Paste in any text editor and get a list of links to the selected bugs.

In addition, you can hit Ctrl+Shift+C (or select Copy ID and Summary from the context menu) to copy the list of bug IDs and summaries to the clipboard — this list can be used as a part of a version control commit message or in release notes.