Yes, please write to sales@almworks.com and we'll be glad to provide you with an extended corporate evaluation license. You can also order a one-time extention of evaluation period on our web-site.
To install the license:
Restart the application for changes to take effect. |
To get the information on different types of JIRA Client licenses, please see a comparison table.
A single-user license is intended for companies and organizations which need the software for general commercial use. Such license allows anybody in the company to use the application and get a standard 1 year support service. Read more about our support services here.
Personal licenses are intended for personal use, and if you are the only person planning to use that license, then the personal license is for you. Personal licenses are non-transferable, and they are not available to companies.
To remove a duplicate row:
Yes, time tracking is supported. To start using time tracking:
As of July 2009, Atlassian JIRA versions 3.3 or newer (any edition) are supported. JIRA 4.0 Beta versions are supported as well.
No additional installations are required on the server side. JIRA should have remote API enabled. It is disabled by default on a freshly installed JIRA, but it is probably already enabled on your JIRA, especially if someone works with JIRA from any remote client.
To enable remote API in JIRA (requires JIRA administrator privileges):
You can find more about it here.
Yes, JIRA Client will pick up custom fields and let you edit and search them. It will automatically load new custom fields during full synchronization, which by default takes place twice a day. To add a custom field immediately, you can enforce a full synchronization. To do so:
To share queries:
To paste a query:
JIRA Client currently does not have this feature but you can remove an attachment using the web interface.
To remove an attachment:
You can remove an attachment which you have just added to an issue but haven't uploaded yet. To do so:
|
You can use the following features to monitor the health of the project:
The reason for that may be that too many issues have been downloaded. Currently JIRA Client can handle effectively up to 20,000 issues. Find more about current limitations here and follow these tips.
This may happen if the config.xml
file is corrupted. This file stores all the queries you make and is located in the workspace directory. By default, it is {{ $HOME/.JIRAClient}}.
Each time JIRA Client starts, config.xml
is backed up into "backup" subdirectory in the workspace.
To fix the problem:
Copy a backed up version of config.xml
file from the backup subdirectory of a workspace. Select the largest file because JIRA Client can have several new backups since the history had been lost.
If the procedure described above do not help, we recommend to clear the database. |
JIRA Client sees only users mentioned somewhere in the issues content. If you don't see a user name in a drop-down list, you can type his or her e-mail address. After that when you edit an issue, the user's e-mail appears in the list.
You can prepare JIRA Client for deployment within a company using the following procedure:
Put the following parameter in the jiraclient.properties file:
jiraclient.license=jiraclient-company.license |
JIRA Client works roughly in the same way as a version control system:
All the fields, comments, links, sub-tasks are downloaded automatically when you first download an issue as a result of a query. Some aspects of an issue such as:
are downloaded using right-click an issue or selecting Issues | Download or when you open an issue for at least 3 seconds.
If you change something in an issue details, your modifications are uploaded when you select Upload or Upload All.