IMS2.0 is a new fully functional version of the popular lightweight web-based bug-tracking system. IMS can be applied to a broad range of problems related to tracking various events in the life cycle of a product >>>

Overview

The role associated with the user "admin" is called the administrator. The administrator is the only user that initially exists in the system, and only this user can access the backend (located in the subdirectory "admin") and some special functions of the frontend.

The administrator performs three major functions:

• defines system settings, such as the name of the SMTP-server, company name, number of links per screen when paging, etc
• activates new users and manages their status in projects
• creates new products (projects) and manages their parameters (severities, statuses and types).

In addition, the administrator is responsible for user mailing and can participate in the incident's life cycle with full rights.

Let's consider the administrator functions in more detail.

One of the administrator functions is to define the list of predefined parameters (bottom left corner). These include:

• "common" parameters: companies and operation systems. Company is the parameter of a product and operation system is the parameter of an incident.
• "product-dependent" parameters (severities, statuses and types) are used to define a complete set of product parameters.

A new product has all of the predefined parameters. These predefined parameters must be changed in order to create a product with different parameters. In the definition of a new parameter, OrderID is the sequential number in the output list.

Backups

The administrator can backup the data, relating some IMS-projects, or create the full backup, containing all IMS-products data. In the first case you have to check the products required, specify the backup file and click on the button "Create backup". By checking no products, you create the full backup, by checking "-----------------", you create an empty backup (containing no product-relating data). The administrator can restore backup from the file (Attention! The current backup will be replaced and the data will be lost).

MySQL command - "mysqldump.exe" creates the backup, "mysql.exe" restores the backup. Settings are recorded in backups/backup.conf.

Settings

All of the settings are initially set at installation time and can be modified later. Correct values of settings (and parameters of the database) are crucial for operation of the system.

• From_Email - email address from which all of the system messages are mailed
• From_Name - the user name from which all of the system messages are mailed
• login_url - complete URI for the front-end (including the directory, e.g., https://ims.sib3.ru/ims/)
• admin_url - complete URL for the back-end (including the directory, e.g., https://ims.sib3.ru/ims/admin/)
• smtp - name of the SMTP-server (e.g., localhost)
• LINKS_ON_PAGES - the number of links per page when paging
• signature - used for the system's email messages
• Company_name - name of the company using this copy of IMS
• Default_language - the language of interface set by default
• Email_CharSet - emails charset
• E_mailer - the way of sending email messages from the server ("sendmail","phpmail","SMTP")

More settings may be added in the future versions.

Status change

Initially there are no constraints for status change in IMS. Another administrator's function is to set the conditions of status change. For that he selects the product, the status and its replacement and finally checks the conditions. This version of IMS suggests the following conditions:

• comments - comment required
• history - history messages required
• logs - log messages required
• files - attachments required
• attach_files - attachments must be specified
• session_creator - the user is a creator of current incident
• session_assigned - the user is assigned to current incident
• assigned_to - owner required
• target_date - target date must be specified
• target_not_empty - target date required
• submitted - the status of current incident is "submitted"
• accepted - the status of current incident is "accepted"
• not predefined - the status of current incident is not "submitted", "accepted" or "closed"
• open - the status of current incident is "opened"
• closed - the status of current incident is "closed"

More conditions may be added in the future versions.

Translation

IMS enables the use of localized versions of the system. However, inintial data stored in the database, is recorded in english. The administrator can display this data in localization language. For that he uses the "translation" block. The administrator enters an enlish word, selects the localization language and then enters the translation.

Users

The administrator receives notifications about each new user registered in the system and activates this user's account. Once this is done, the user will be able to log in, but will not have access to any projects. Therefore, the administrator must associate the user with the required products, i.e., define the user's status (assign to user group). This can be done either on the user's page or on the product page.

In the worst case the administrator can delete the user from IMS, but usually it is enough to disactivate user's account.

Only administrator can access all of the user's data (except for the password) and make them available to the product manager if needed, to overcome a limitation of IMS.

The administrator also can give a special status to the user, allowing the user to "see" the names of other users with "higher" roles.

Groups

The administrator can create and delete the user groups. To define a group means to define the rights of group members. Regarding an incident, there are 3 more attributes:

• user - the creator
• user - the owner
• other

The administrator sets the visibility possibilities and available actions, marking checkboxes on the group page. On the opposite, an empty checkbox means that the action is prohibited. For example, almost all actions are prohibited by default for the "unsigned" user group.

Products

To begin the creation of a new product, the administrator checks and changes its predefined parameters (severities, types and statuses). Some status values of an incident cannot be changed or deleted; these are "submitted", "accepted", and "closed".

To create a new product, only its short name must be specified. Product description and customer (selected from a list) are optional. Once a product has been created, the administrator can manage its users and establish their roles in the product's page.

Also on the product's page, the administrator can change the names of the product parameters and the name of the product itself. Severities or status values and types can be added and deleted (except for some special values).