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.
DescriptionGarik Khachikyan
2011-11-04 11:44:35 UTC
Description of problem:
Right now there is displaying the whole list of notifications happening for all the orgs.
I think it's not right - dividing them between orgs would be better.
Version-Release number of selected component (if applicable):
katello-0.1.98-1.git.13.5a8e341.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. try to perform different operations (like importing manifest files for different organizations) for different orgs.
2. check logs - for both orgs the "Notifications" are exactly the same.
3.
Actual results:
Can not check to which org the notification belongs.
Expected results:
Should be separated between orgs.
Additional info:
We have removed katello notifications from the code base, so this bug is no longer relevant. This should be closed as NOTABUG, but moving to ON_QA for verification / knowledge.