Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6870

[3scale][2.11][HI-prio] Improve Select in 'Add Backend to Product' form

XMLWordPrintable

    • 8
    • False
    • False
    • Yes
    • Undefined
    • 3scale-doc-2021-06-21, 3scale-doc-2021-07-12

      User Story

      As an API Provider, I want to easily find a Backend when I'm trying to add it to a Product.

      Requirements

      • Move CTA to Add a Backend out of the table header, and into the page header
      • Add PF4 primary button style to CTA
      • Form:
        • Turn Backend select into a Typeahead select
        • Turn Create Backend link into a link button with icon (PlusCircleIcon){{}}
        • If CTA to create a new Backend is clicked, open a modal dialog displaying the New Backend form
          • 'Create Backend' modal:
            • Only activate submit button when all the required info has been entered
            • keep same inline errors already present in the full page New Backend form{{}}
        • When Backend select is clicked, display 20 most recently created Backends in dropdown menu (sorted by most recent)
          • Backends already added to the Product should not be displayed 
          • If the sum of all Backends available is higher than 20, display link button to "View all Backends"
        • When "View all Backends" is clicked, open a modal dialog that includes a paginated table listing all Backends
          • 'Select a Backend' modal: 
            • display 5 Backends per page
            • sort table by last updated by default
            • make table filterable by Backend name
            • Backends already added to the Product should not be displayed
            • When one Backend is selected enable "Add" submit button
        • When the modal dialog is submitted, automatically select the Backend and display it in the Select
        • When Backend is selected, enable the "Add to Product" submit button
        • On submit, if specified Path is not available throw an inline error

      Resources

      • Path: Product > Integration > Backends
      • Marvel

      Acceptance Criteria

      • All requirements have been implemented

            Unassigned Unassigned
            acontini Alessandro Contini
            Dominik Hlavac Duran Dominik Hlavac Duran
            Jose Miguel Gallas Olmedo Jose Miguel Gallas Olmedo
            Alessandro Contini Alessandro Contini
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: