Issues for Alerts Management Service 1.0 (ALMAS) Finalization Task Force

To comment on any of these issues, send email to [email protected]. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to [email protected].

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Jira Issues

Issue 13031: Section 7.3 hierarchy Jira Issue ALMAS-1

Issue 13031: Section 7.3 hierarchy (almas-ftf)

Click here for this issue's archive.
Nature: Revision
Severity: Critical
Summary:

Section 7.3: The hierarchy is defined in the Receiver Hierarchy Configuration File and is alert independent, so for all templates the same. Therefore RKParentType should be removed from ReceiverKind related to AlertTemplate in order to prevent a lot of redundant information. Solution: Remove RKParentType from ReceiverKind related to AlertTemplate.Instead, introduce a seperate class ReceiverHierarchy. Note that this has quite an impact on the PSMs!

Resolution:
Revised Text:
Actions taken:
October 31, 2008: received issue
April 30, 2009: Deferred

Discussion:

This change would have a significant impact upon the PSMs and as such it was deferred.  There may be some redundant information as a result of this.    Suggest handled in an RTF