| Type | Description | Detail level of body text | Example |
|---|---|---|---|
| All changes | This type of notification contains information
about the latest changes that were made to the elements in the view.
For example, the owner of a requirement might set up this type of
requirement to be notified each time the requirement changes. To set up this type of notification, the history logs of the attributes in the view must be activated. You can activate history logs on the Attributes page of the Configure menu. If no elements have changed since the last time the notification was sent, no notification is sent. Note:
There might be multiple changes on each element. The messages
are grouped by elements that have undergone similar changes. The notification
message starts with a link to an element that changed with a description
of the change, followed by the links to elements that have undergone
similar changes.
|
|
[ATTRIBUTENAME] for [ELEMENTLINK] has been changed
to [ATTRIBUTEVALUE] by [USERNAME] [TIME]. Click the link to go to
the requirement. This notification might be displayed as follows: Status for Req1234:Example Requirement 1 has been changed to Implemented by John Smith 2007-07-04 12:37. Click the link to go to the requirement.Example of notification that are grouped by elements that have similar changes:
|
| All current content | This type of notification is about the content of a view and is sent at a specified interval. For example, to track all new requirements, a product manager might set up a weekly notification that contains the requirements with the "New" status. |
|
This notification might be displayed as follows:
|