# WebIssues Manual

## Version 1.1.3

Home » Tracking issues
« Tracking issues
Subscriptions »

## Managing alerts

Even if you are using views and unread statuses of issues, it's not always visible at the first glance that there is a new or modified issue that requires your attention. Because of that, the WebIssues system has a mechanism of alerts, which are automatic notifications about unread issues that meet certain criteria.

You can create an alert using any public or personal view, as well as the built-in “All Issues” view. Each alert is assigned either to a specific folder or a global list of issues of a given type.

Suppose you want to keep an eye on all active bugs and tasks. Open the Bugs folder and select Manage Alerts. The list of alerts is initially empty, so choose Add Alert to define a new alert for this folder.

Figure 4.3. Adding an alert

Select the “Active Bugs” view and click OK. The list now contains a new alert, and also displays the total number of all issues that meet the criteria of the view, and the number of unread and modified issues.

Figure 4.4. List of alerts

If the alert contains unread issues, its icon will change to a closed, yellow envelope. Similarly, if it contains a modified issue, a green envelope will be displayed. So by opening the alerts window, you can quickly see if there are any issues which require your attention.

Now repeat the same steps to create an “Active Tasks” alert in the Tasks folder. If you are using the Desktop Client, you will notice that the alerts are visible in the projects and folders tree:

Figure 4.5. Tree with alerts

The program periodically updates the contents of all folders for which you've defined alerts, so you can track their status almost in real time. If in any of the views there are some unread issues, the icon of the alert will be changed, its name will become bold, and the number of new and modified issues will appear in parentheses:

Figure 4.6. Tree with active alerts

If you click on an alert in the tree, not only the folder, to which the selected alert belongs, will be opened, but also the view associated with this alert will be automatically selected. This mechanism is therefore very helpful in everyday work.

### Email notifications

If sending emails was enabled in the WebIssues system, you can configure the way of sending notifications for each alert.

### Note

For more information about configuring sending emails read the section called “Sending emails”.

There are three types of notifications available in the WebIssues system:

Immediate notifications

  Sent immediately when someone adds or changes an issue which meets the criteria of the alert.

Summary of notifications

  Sent at specified days and hours, if someone adds or changes issues related to the alert.

Summary reports

  Always sent at specified days and hours, regardless of whether any changes have occurred.

The type of notification can be specified when you create an alert, as long as sending emails is enabled on the server. You can also change it at any time for an existing alert. To do this, select the alert in the alert management window and select Modify Alert.

Figure 4.7. Changing an alert

Immediate notifications are useful if you want to be kept informed of any changes, and you don't use the WebIssues system all the time. The frequency of sending immediate notifications depends on the configuration of cron job on the server. It can vary from once in a few minutes to once an hour. If an alert generates too many notifications, or if they are not very urgent, you can choose a summary of notifications instead, to receive aggregated information about recent changes, for example, once a day.

Summary reports contain a list of all issues, regardless of whether they have been changed since the last notification, and whether they were read by you. They are useful if you want to track the status of all issues that meet specific criteria, for example, to check whether the active bugs are being solved continuously.

Summary notifications and reports are sent at the selected days and hours. Depending on your needs, you can receive a summary email once a week, several times a week, once a day, or several times a day. You must select at least one day and one hours when configuring a summary email.

### Note

In version 1.0 the summary schedule was configured globally in the user preferences. When updating to version 1.1, the schedule settings are automatically migrated to individual summary alerts.

In order to receive notifications, you must change your user preferences. If you are using a browser, click Tools and then User Preferences. To change them in the Desktop Client, select User Preferences from the main window toolbar.

Figure 4.8. Notifications settings

Enter a valid email to which the notifications will be sent. Select Include issue details in notifications and summary reports, if you want the emails to contain also issue details and the history of changes and recently added comments and attachments. Otherwise only a summary of issues will be sent.

Select Do not notify about issues that I have already read if you don't want to receive notifications about issues that you've read (for example, if you created or modified them by yourself). Also issue details that you've read, will not be included in that case. This option doesn't affect summary reports, which always contain all issues and changes.

### Warning

You won't receive any notifications if you don't set the correct email address in your user preferences.

All email notifications include the name of the associated project, folder and alert in the header, and also the list of issues. The list contains the same columns as the view which is associated with the alert.

Figure 4.9. An email notification

If you selected the appropriate option, email notifications will also include details of each issue, similar to the issue details view in the main window of the program.

### Tip

Instead of configuring a separate alert for each folder of a given type, it may be more convenient to create a single alert associated with a global list of issues. To create and manage global alerts, open the global list of the appropriate type and select the Manage Alerts command. An additional advantage is that only a single email notification is sent containing all new and modified issues, instead of separate emails for each folder.

### Public alerts

Project administrators and system administrators have the ability to create public alerts which are shared by all users. For example, if you want all users to keep track of active bugs assigned to them in a specified folder, open the folder, select Manage Alerts and then select Add Public Alert. Choose the “My Active Bugs” view from the list and click OK.

Figure 4.10. List of alerts with a public alert

All users will now see the alert in their project tree in the Desktop Client. Public alerts can be distinguished from personal alerts by a small user symbol in the corner of the icon.

You can configure email type and schedule for a public alert in order to enable sending email notifications. Notifications for public alerts associated with a folder are sent to all users who can access the folder, regardless of whether or not they are explicitly listed as project members. If the folder belongs to a public project, notifications are sent to all active users. Notifications for public alerts associated with a global list of issues are sent to all active users who have access to at least one folder of the given type. Only users who have a valid email address configured in their user preferences will receive email notifications.

### Note

Summary notifications for public alerts are always sent according to the server's time zone, and the time zone preferences of individual users are ignored. However, other preferences, such as including issue details in notifications and summary reports and ignoring notifications notify about issues that the user has already read, are respected for each individual user.

A public alert can be associated either with a public view or the “All Issues” view. It cannot be associated with a personal view; you have to publish the view first to make it available to all users.

Regular users are not allowed to delete or modify settings of a public alert. Also they cannot create a personal alert associated with the same view as the already existing public alert. When a public alert is created, all personal alerts associated with the same view are deleted.

### Tip

Setting up a large number of public alerts may cause a lot of emails to be generated. You can restrict the number of emails by using appropriate view conditions; for example users can only receive notifications about issues which are currently assigned to them. Use global alerts when possible, instead of creating separate alerts for each folder. Also consider using summary notifications instead of immediate notifications.

« Tracking issues
Subscriptions »