This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2125806 - Can't select all errata from content>errata submenu
Summary: Can't select all errata from content>errata submenu
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Satellite QE Team
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-10 16:09 UTC by Matthew Yee
Modified: 2024-06-06 12:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:30:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36712 0 Normal Assigned Can't select all errata from content>errata submenu 2023-08-31 17:53:35 UTC
Github Katello katello pull 10715 0 None open Fixes #36712 - Add true select all to errata legacy UI 2023-08-31 18:07:00 UTC
Red Hat Issue Tracker   SAT-18046 0 None Migrated None 2024-06-06 12:30:54 UTC

Description Matthew Yee 2022-09-10 16:09:25 UTC 
Description of problem:
Can't select all errata to be applied from the Content>Errata menu. 

Version-Release number of selected component (if applicable):
6.12

How reproducible:
100%

Steps to Reproduce:
1.Mouse over "content".
2.Click errata.
3.Click checkbox for all errata. 

Actual results:
20 errata will be selected. You can change the pager to show 100 errata but if you have more than that, you'll have to select all errata manually. I'm aware that a better method for applying errata is through Collections however this is just not a great experience for the user.

Expected results:
Select all errata.


Additional info:
If you apply errata through collections, there is an option to select all errata. Can we make that available as well as an option to schedule the application of all errata like through collections?
Comment 1 Matthew Yee 2022-09-10 16:13:26 UTC 
Link to video showing the problem.
https://drive.google.com/file/d/1bQdW-YW-tN5X_H-nAZvsEbJlZG95hzea/view?usp=sharing
Comment 5 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 8 Eric Helms 2024-06-06 12:30:56 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.