Bug 1263689 - Inconsistent naming Content Notices vs. Notifications
Summary: Inconsistent naming Content Notices vs. Notifications
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Ohad Levy
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2015-09-16 12:20 UTC by Peter Vreman
Modified: 2019-09-26 13:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-15 23:39:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter Vreman 2015-09-16 12:20:40 UTC
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:

Comment 1 Brad Buckingham 2015-10-15 23:39:49 UTC
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.

Comment 2 Peter Vreman 2015-10-19 10:24:01 UTC
Confirmed that it is unused. I have (mail) errata notifications working, but the Content Notices are still empty.


Note You need to log in before you can comment on or make changes to this bug.