Project

General

Profile

Bug #24550

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

Added by Walden Raines about 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

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.

Associated revisions

Revision a7eebfff (diff)
Added by Avi Sharvit almost 2 years ago

Fixes #24550 - Search repo by products

Revision ed80ad41 (diff)
Added by Walden Raines almost 2 years ago

Refs #24550: move export csv button to enabled col

Move the export csv button to the enabled repositories column.

https://projects.theforeman.org/issues/24550

History

#1 Updated by Tomer Brisker about 2 years ago

  • Category set to Repositories
  • Project changed from Foreman to Katello

#2 Updated by Marek Hulán about 2 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.

#3 Updated by Walden Raines about 2 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.

#4 Updated by Justin Sherrill about 2 years ago

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

#5 Updated by Tomáš Strachota about 2 years ago

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

#6 Updated by Avi Sharvit about 2 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?

#7 Updated by Tomáš Strachota about 2 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.

#8 Updated by Tomáš Strachota about 2 years ago

  • Team Backlog UX added

#9 Updated by Walden Raines about 2 years ago

  • Assignee set to Avi Sharvit

#10 Updated by Avi Sharvit about 2 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)

#11 Updated by Walden Raines about 2 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.

#12 Updated by The Foreman Bot about 2 years ago

  • Pull request https://github.com/Katello/katello/pull/7702 added

#13 Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing

#14 Updated by The Foreman Bot about 2 years ago

  • Pull request https://github.com/Katello/katello/pull/7717 added

#15 Updated by Walden Raines about 2 years ago

  • Pull request deleted (https://github.com/Katello/katello/pull/7702)

#16 Updated by Walden Raines about 2 years ago

  • Assignee changed from Avi Sharvit to Walden Raines

#17 Updated by Zach Huntington-Meath about 2 years ago

  • Target version changed from Katello 3.9.0 to Katello 3.10.0

#18 Updated by Anonymous almost 2 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF