Admin Tools for JIRA [1.5.x]



Description of functionality Admin Tools for JIRA.

Using the extension of Admin Tools for JIRA provides you, among other features, with the ability to generate reports on the number of existing projects and users without a need to do this manually. There are no options in the standard system, which would enable an easy and quick way to learn how many projects are currently in use, which ones generate the most traffic, or even how many tickets there are in each of them. Every administrator, as well as many managers, need an access to such information, in order to optimally plan the development and financing of support systems. Having been exported to Excel, the data can be used in a way of your choice: for a presentation, for a report or purely informatively for regular monitoring of usage of the system. Both functions have similar objectives, and allow full configuration according to your requirements. Export of projects / users is a feature desired by others for several years, for example.

Sending notifications about the upcoming action to users solves the problem of lack of information on the part of administrators, when there is a need of a sudden rebooting, for example. Notifications come automatically, without reloading the page and allow you to prepare for the upcoming action. Administrators can set a timer that gives users time to save current changes, export the most important data and peaceful logout. Using this feature reduces the need to prepare a separate message, lets you avoid sending unintentional emails, and thus effectively increases user's satisfaction. Till now, most likely, no one has come up with this way of informing about the upcoming changes.

The function of checking whether the custom field is used in the system, is extremely helpful during cleaning up the system. Incompetent management of the system and an increasing number of custom fields on a request may, eventually, lead to a situation when administrators will need to do the cleaning. Users very often ask for a change in the configuration, however, it turns out that many fields have not been used. The number of objects, in particular, the number of custom fields, drastically affects the performance and stability of the application. The knowledge, whether or not, the added field has been used in the system, reduces the time needed to make a decision on removing of the field, and the action itself does not require that additional data backup be performed. Deletion of custom fields is, in fact, subject to extremely high risk of losing data. Knowing potential problems administrators do not take such decisions without additional information.

The ability to copy the settings of the field, also gives you huge time savings. Users often request to create a field that will have similar functionality to a currently used one. Creating a field from scratch and assigning it to the same project and the screens, where it appears, is now a very tedious process and not always easy to perform smoothly. Backing up the field, basing on a currently existing one, eliminates these problems and allows users to provide the required fields three times faster.

Installation [1.5.x]

Use case scenarios