Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1216

Create a tool for importing SBO performance test KPIs data into Segment

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • QE, Service Binding
    • None

      Owner: Architect:

      _<Architect is responsible for completing this section to define the
      details of the story>_

      Story (Required)

      As a user I would like to be able to import SBO performance test results data into the Segment service for storing and to be visualized by Woopra dashboard

      _<Describes high level purpose and goal for this story. Answers the
      questions: Who is impacted, what is it and why do we need it? How does it
      improve the customer’s experience?>_

      Background (Required)

      <Describes the context or background related to this story>

      Glossary

      <List of new terms and definition used in this story>

      Out of scope

      <Defines what is not included in this story>

      In Scope

      <Defines what is included in this story>

      Approach(Required)

      _<Description of the general technical path on how to achieve the goal of
      the story. Include details like json schema, class definitions>_

      Demo requirements(Required)

      _<Description of demo which would show the value of this story. Any demo
      should also be included as part of the acceptance criteria.>_

      Dependencies

      _<Describes what this story depends on. Dependent Stories and EPICs should
      be linked to the story.>_

      Edge Case

      _<Describe edge cases to consider when implementing the story and defining
      tests>_

      Acceptance Criteria

      _<Provides a required and minimum list of acceptance tests for this story.
      More is expected as the engineer implements this story>_

      Development:

      • A tool capable of importing the KPIs into the Segment is available

      QE:

      Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

      Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
      Applicable

      Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
      Applicable

      Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
      fix/Breaking change/Deprecated Functionality/Technology Preview>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

            Unassigned Unassigned
            pmacik@redhat.com Pavel Macik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: