Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-928

Add @backstage/plugin-scaffolder-backend-module-notifications as community plugin

Create Doc EPIC from R...Prepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Feature Overview (aka. Goal Summary)

      An elevator pitch (value statement) that describes the Feature in a clear,
      concise way.

      RHDH includes the notifications plugin, which is enabled by default, but doesn't include the scaffolder backend notification plugin. By adding it as a community plugin, we would make it easier for customers to utilize it, and send notifications directly from scaffolder templates, and can start gathering feedback to see if it should be more tightly coupled in the future.

      Goals (aka. expected user outcomes)

      The observable functionality that the user now has as a result of receiving
      this feature. Include the anticipated primary user type/persona and which
      existing features, if any, will be expanded.

      Make it easier for customers to utilize notifications from scaffolder templates.

      Requirements (aka. Acceptance Criteria):

      A list of specific needs or objectives that a feature must deliver in order
      to be considered complete. If the feature spans across releases then good
      to have scope for each release with acceptance criteria. Be sure to
      include nonfunctional requirements such as security, reliability,
      performance, maintainability, scalability, usability, etc.

      • @backstage/plugin-scaffolder-backend-module-notifications is added to RHDH as a community plugin
      • Plugin lists are updated as needed
      • Catalog metadata is provided so it can be discovered and installed via the marketplace
      • Update our plugin maintenance tasks to have it track backstage updates

      Out of Scope (Optional)

      High-level list of items that are out of scope.

      Productizing it directly as a more supportable DP/TP/GA tier. 

      Customer Considerations (Optional)

      Provide any additional customer-specific considerations that must be made
      when designing and delivering the Feature. Initial completion during
      Refinement status.

      <your text here>

      Documentation Considerations

      Provide information that needs to be considered and planned so that
      documentation will meet customer needs. If the feature extends existing
      functionality, provide a link to its current documentation.

      Update catalog metadata and any relevant plugin lists

              Unassigned Unassigned
              mreid1@redhat.com Matt Reid
              RHDH Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: