JIRA Client lets you search, view, modify and create issues even when you are offline, when JIRA server is not reachable, or when you have a slow VPN connection.

This is made possible by a local database of downloaded issues, maintained by JIRA Client. You change the local copy of an issue, and JIRA Client tries to upload the change when possible. In case of a conflict, JIRA Client offers you to merge conflicting changes field-by-field.

Offline search is supported by synchronized queries — search requests that JIRA Client has already downloaded before. To keep synchronized queries up to date, JIRA Client periodically polls the server for issues updated recently.

You can set up multiple connections to different JIRA servers and have a centralized place to work with issues from them all.

In JIRA Client, queries are the starting point for working with issues. A query filters issues 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 issues into manageable subsets.

If your queries are synchronized, JIRA Client also shows the number of issues that satisfy each query at the current moment. This provides you with a quick overview of the current state of the work.

A distribution by field groups issues by their values in that field. Essentially, a distribution is a number of sub-queries, each sub-query showing only the issues with a specific value in the field.

You can quickly build distributions by Status, Assignee, Priority and other fields, and you also can nest one distribution under another. This lets you quickly get to the issues you're interested in, while preserving context in the navigation tree.

Another type of distribution, 2D Distribution, works in the same way, but it groups issues by two (or even more) fields.

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

If you drag an issue and drop it on a query in the navigation area, JIRA Client will try to change the issue to make it satisfy the query's filter.

You can think of it as if you're actually moving the issues 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 issues just by using drag and drop.

So if you do a lot of triage, or evaluating and assigning issues, you can set up a number of queries that represent your typical changes to an issue, and then just drop the issues on them.

JIRA Client lets you quickly search for issues containing specific words, within a scope — the search is done among the results of the currently selected query.

JIRA Client's search engine finds issues that contain exactly the words (or parts or words) that have been entered in the search field. This provides better quality of the search results in most cases, and makes it possible to search for unusual sequences of characters.

JIRA Client also has in-table search, opened with Ctrl+Shift+F keyboard shortcut, which looks for specified text in the issue table. The in-table search is capable of looking for complex search terms specified by a regular expression.

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

Later, you can review the time sheet, make corrections and publish tracked time to JIRA as work logs.

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

With JIRA Client it is very simple to capture a screenshot and attach to an issue.

Screenshot editor lets you crop the image, blur regions with sensitive data, highlight and magnify areas with problems, and add comments on the screenshot.

JIRA Client lets you define tags and apply them to issues. Tags are similar to JIRA's labels, but they are stored in the local database and never uploaded to JIRA.

You can use tags to create groups of issues that cannot be defined with a query. For example, you can tag issues that you'd like to address in the next iteration.

You can group issues from different JIRA connections with a single tag, and tags also may be used in building queries.

Select multiple issues in JIRA Client and use Copy to place the issues 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 issues.

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