Parent Project
About
Building
Running
Using
Project Documentation
Modules
- System Base Module
- User Module
- Project Module
- Incident Data Module
- Accounting Module
- Webclient Module
- DB Bindings Module
- Snippets Library Module
This guide assumes a local installation of a Naggregator installation - please modify the stated URLs according to your Naggregator installation (http://yourhost/nag-web-jsp/* instead of http://localhost/nag-web-jsp/*). Furthermore, you need to register a user account at the Naggregator instance.
As a naggregator instance drops incident reports for unknown projects, you need to register a project before starting to deliver incident reports. The registration is performed using the project registration form which is accessible for every registered user (in role 'project_user').
Registering a project requires the user to provide, next to a project name, a project group id which establishes a fix personal name space for every user to prevent a clash of equally name projects.
While a project is basically just a container for incoming incident reports, there are some some organisational aspects that need to be dealt with, namely access control for project members, a possible synchronization target and regular notification reports that might need to be setup.
Initially, a project has exactly one member (the 'founder') but since most projects have more then 1 developer and non-technical contributors, you can assign multiple user accounts to a registered project (requiring that every contributor has a registered user account at the Naggregator instance).
Every member of a project is subject to project related role which has to be assigned by a project maintainer. The following roles are assignable:
| Observer | An observer can see the project, the project description, received tickets and subscribe to active notifications. |
| Developer | A developer has all rights of an observer and can delete tickets. |
| Maintainer | A maintainer has all rights of a developer. Furthermore he can order upgrades, change the project data and enable notifications for the project. |
The Member Management for all registered projects is accessible via the Project Overview.
Naggregator has a build-in functionality for the automated forwarding of Incident reports to Issue Managing Applications. This can be setup using the Synchronization Management Page (available via the extended Project Overview). The synchronization requires a supported Issue Manager (currently only uncustomized Bugzilla 2.18 - 3.0).
The following steps are necessary for the setup of a bugzilla synchronization:
Hint: You might experience, that a connector remains in state "Invalid Configuration" after a remote lookup. If you can ensure that the given credentials are correct, such a behaviour indicates that the remote Bugzilla instance is not supported as Naggregator can only successfully communicate with unmodified Bugzilla instances just like the demo installations listed under http://landfill.bugzilla.org.
Notification reports are regular reports created by the system. While a project member in role "Project Maintainer" can en-/disabled the available reports, every project member can subscribe to the enabled reports. The following reports are available:
| Daily Quota Load Warn Report | If your ticket quota exceeds the 90% mark or reaches the 100% limit you will get a warning message as the system rejects new incident data upon the reaching of the quota. This message will be send every 24h until the quota usage is sanitized. |
| Daily New Tickets Report | This daily report gives an overview of new tickets and incidents. The report is only send when new tickets/incidents have been received. |
All options regarding notification are available on Notification Configuration Page which is linked on the Project Overview Page.
There are 3 regulations (quotation, notifications, synchronization) per project controlling the resource consumption on the Naggregator instance, helping the system to deliver equal service to all registered users.
These regulations are determined by Regulation Profiles which may be valid for a limited time. While a project can be subject to multiple Regulation Profiles simultaniously, only the best/highest profile is active at a specific time while lower profile remain pending.
Every regulation can be upgraded by a project member in role "Project Maintainer" to a better profile using the Project Upgrade Form; depending on the usage scenario and configuration, the upgrades are free or available for a fee.
Every project is subject to a Quota Regulation which controls the max amount of stored incident, tickets, attachments and properties (an explanation of the data model can be found in the Incident Management Guide. You can inspect the current Quota Profile using the Extended Project Overview.
Please make sure to remove unused known and fixed tickets as the Naggregator instance will drop incoming reports that exceed the quotation.
The Notification Regulation controls the available notification reports. You can inspect the current profile using the Extended Project Overview.
Notifications are regular reports send per mail. They inform the user about recent incident reports or quotation warnings.
The Synchronization Regulation controls the available synchronization target systems and furthermore the minimal interval between synchronization sessions. You can inspect the current profile using the Extended Project Overview.