Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5837

RHACS: Customizing / editing email notification templates

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • ACS Notifiers, RHACS
    • False
    • None
    • False
    • Not Selected

      Business Problem:

      _Customer would like to see changes to the contents of email notifications. Current notification contents include irrelevant / misleading information and is missing one or more necessary attributes.
      _

       

      Use Cases:

      Customer wants to notify recipients of policy violations, without including an Alert ID or Alert URL. Alert IDs are long strings that they consider irrelevant and confusing. Alert URLs provide a link to ACS Central UI, which they consider irrelevant and confusing, because they do not intend to provide access to the Central UI to users.

      Customer will be using multiple Centrals due to scale. Customer would like to add the Central name where the notification originated, for tracking purposes.

       

      Key Functionality:

      [Outline the main functions and capabilities of the feature]

       

      Benefits:

      [Highlight the benefits/advantages of the suggested feature if not addressed above]]

      Acceptance criteria:

      [Describe the key features that need to be covered by the feature to be able to satisfy the customer]

      Implementation Suggestions (optional):

      • Integration: [Specify any existing systems or tools that the new feature should integrate with]

       

      • Dependencies: [Describe any dependencies on other 3rd party integrations or OCP components] 

       

      • User Experience: [Provide suggestions for designing the UI to optimize usability. Highlight other relevant aspects of the user experience ]

       

      Timeline:

      [Specify the preferred implementation date or any specific deadlines for the feature implementation]

       

      Please use the following Jira fields to complete this Feature Request

      1. [Jira Field] Summary Required: [Provide a clear and concise name/description for the feature]
      2. [Jira Field] Description:
      3. [Jira Field] Component:
      4. [Jira Field] Priority: [Indicate the importance or urgency of the feature on a scale of High, Medium, or Low]
      1. [Jira Field] Supporting Documentation:
         
      1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]

       

       

            bmichael@redhat.com Boaz Michaely
            cporter@redhat.com Christopher Porter (Inactive)
            Anjali Telang, Boaz Michaely, Doron Caspin, JP Jung, Maria Simon Marcos, Shubha Badve
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: