Bug #24550: Search and enable new repo on Red Hat Repositories page is tedious task - Katello - Foreman

Actions

Copy link

Bug #24550

closed

Search and enable new repo on Red Hat Repositories page is tedious task

Added by Walden Raines over 5 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

High

Assignee:

Walden Raines

Category:

Repositories

Target version:

Katello 3.10.0

Difficulty:

Triaged:

Yes

Bugzilla link:

1608006

Pull request:

https://github.com/Katello/katello/pull/7717

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1608006

For the customers using a large set of Red Hat products, it is really difficult to filter out and get a specific repo for the required product and required RHEL version.

Example: The customer wants to search and enable the Jboss repository, they can use a search query as: "name ~ Jboss", it provides them 13 page result. We can change the per page entry option to 50 but still, they have to scan through 5 pages to get the repo.

There are less chances that users will have the repo label handy to search the repo in the search bar.

Files

Screen Shot 2018-08-14 at 9.30.43 AM.png

View Screen Shot 2018-08-14 at 9.30.43 AM.png

37.8 KB

Tomáš Strachota, 08/27/2018 10:16 AM

Actions

Copy link

Updated by Tomer Brisker over 5 years ago

Project changed from Foreman to Katello
Category set to Repositories

Actions

Copy link

Updated by Marek Hulán over 5 years ago

Walden, we moved to Katello project as the BZ seemed specific for katello page. What is the desired change in this case? In Foreman pages, the ordering seems to be reasonable looking at puppet classes for example. I think it would help to summarize what's the expected resolution. Also to set BZ expectation correctly.

Actions

Copy link

Updated by Walden Raines over 5 years ago

Marek Hulán wrote:

Walden, we moved to Katello project as the BZ seemed specific for katello page. What is the desired change in this case? In Foreman pages, the ordering seems to be reasonable looking at puppet classes for example. I think it would help to summarize what's the expected resolution. Also to set BZ expectation correctly.

Sorry, I was copying a bunch of bugs from bugzilla and accidentally moved this into foreman rather than katello. Thanks for moving.

Rox is working on a mockup for this issue but basically we want to show another dropdown for products with a search (see data live search here - https://rawgit.com/patternfly/patternfly/master-dist/dist/tests/bootstrap-select.html). This will allow users to search for a product first similarly to how the legacy page worked.

Actions

Copy link

Updated by Justin Sherrill over 5 years ago

Target version set to Katello 3.9.0
Triaged changed from No to Yes

Actions

Copy link

Updated by Tomáš Strachota over 5 years ago

File Screen Shot 2018-08-14 at 9.30.43 AM.png Screen Shot 2018-08-14 at 9.30.43 AM.png added

I'm adding a screenshot of a mockup by Roxanne.

To sum it up:

We need to add data live search component for filtering repositories by product (please find link in Walden's comment above)
Move existing repo type and the new product filter below the search input
The mockup is missing the CSV export button, but it should remain in the right column where it's now

Actions

Copy link

Updated by Avi Sharvit over 5 years ago

Tomáš Strachota wrote:

I'm adding a screenshot of a mockup by Roxanne.
To sum it up:

We need to add data live search component for filtering repositories by product (please find link in Walden's comment above)

Move existing repo type and the new product filter below the search input

The mockup is missing the CSV export button, but it should remain in the right column where it's now

I need some more information about this feature.

1. What are the select options?
2. Does it multiselect?
3. How does it affect the API Call/Query?
4. Does it requires server side changes?

Actions

Copy link

Updated by Tomáš Strachota over 5 years ago

I need some more information about this feature.

1. What are the select options?

The select should list all products in the current organization.

2. Does it multiselect?

I don't think it's required.

3. How does it affect the API Call/Query?

It needs to append a condition for filtering by the selected product.

4. Does it requires server side changes?

I'm not aware of any.

Actions

Copy link

Updated by Tomáš Strachota over 5 years ago

Team Backlog UX added

Actions

Copy link

Updated by Walden Raines over 5 years ago

Assignee set to Avi Sharvit

Actions

Copy link

#10

Updated by Avi Sharvit over 5 years ago

Tomáš Strachota wrote:

I need some more information about this feature.

1. What are the select options?

The select should list all products in the current organization.

I am having a list of 143 different products on my env.

Should I filter the relevant/recommended by some query?
Or
Should we allow the user to filter them with a search box? (like the breadcrumb switcher)

Actions

Copy link

#11

Updated by Walden Raines over 5 years ago

Avi Sharvit wrote:

Tomáš Strachota wrote:

I need some more information about this feature.

1. What are the select options?

The select should list all products in the current organization.

I am having a list of 143 different products on my env.

Should I filter the relevant/recommended by some query?
Or
Should we allow the user to filter them with a search box? (like the breadcrumb switcher)

Followed up on this during iteration planning but just wanted to say here that we are planning on just having a list of all products in the dropdown for this initial pass at the feature. We can add a search box later if necessary/required.

Actions

Copy link

#12