Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In the Administration menu "Content Notices" is used.
In the User account settings the word "Notifications" is used.
Are these the same? Is Notifications more than Content Notices?
Why is "Content Notices" under Administration and not under "Content" as the name implies?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Look at the UI
2.
3.
Actual results:
Expected results:
Additional info:
The use of 'Content Notices' was due to how it originated in the upstream. In the upstream, Katello had 'Notices' and as part of the enginification efforts of Katello they were labelled as 'Content Notices'. As workflows have moved towards using Dynflow, the usage of the notices was reduced and in the upstream they were ultimately removed. This removal will take place in Satellite 6.2. Based on that, I am going to close this particular bug as 'UPSTREAM' to indicate that the upstream changes make it no longer valid.