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 760180 - Notifications should note the appropriate Org for org-specific actions.
Summary: Notifications should note the appropriate Org for org-specific actions.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Petr Chalupa
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 15:37 UTC by Corey Welton
Modified: 2019-09-25 20:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Organization specific changes appeared out of context in the notification messages. This made it hard to reference changes for organizations. Notifications now refer to the appropriate organization for specific actions or changes.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:41:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Corey Welton 2011-12-05 15:37:11 UTC 
Description of problem:
When applying some change that is org-specific (i.e., creating a new GPG key), it could appear out of context in the notification, like it is system wide. For org specific actions, we should append/prepend the notification somehow to indicate the org for which this action took place.

Obviously GPG is just an example. It should be a general design pattern that is applied to any org-specific action/notification.

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


How reproducible:


Steps to Reproduce:
1.  Create a new org, "BACME_Corporation" with a third party provider and product
2.  In the original org (ACME), create a new GPG key called "Fedora 16"
3.  Switch to BACME_Corporation
4.  In BACME, create a new GPG key called "fedora 16"  
6.  Nav to the notifications view and/or Dashboard > Latest Notification.

Actual results:
"GPG Key 'fedora 16' was created." appears both times it is created.

Expected results:
Something like
[ACME_Corporation] GPG Key 'fedora 16' was created.
[BACME_Corporation] GPG Key 'fedora 16' was created.

Additional info:



< bbuckingham> cswiii, jrist, in the bz, rather than prepend text for the org, may be better to store the org in the model...  
< bbuckingham> in case org name were to change... or we wanted to do some searching based on notices for an org...etc
Comment 1 Mike McCune 2012-01-26 19:39:14 UTC 
mass move to CFSE product.
Comment 2 Petr Chalupa 2012-09-06 09:34:31 UTC 
fixed in a6846e21a1ad3ff8667d7d18981206e487ac82ed
Comment 5 Corey Welton 2012-09-17 16:05:43 UTC 
QE Verified.

CloudForms System Engine Version: 1.1.12-7.el6cf
Comment 7 errata-xmlrpc 2012-12-04 19:41:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Note You need to log in before you can comment on or make changes to this bug.