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.

Take the example of the following issue http://projects.theforeman.org/issues/6807
1. create a host collection
2. add two new hosts to host-collection
3. Go to the host collections index page. 
Notice that the content hosts count has not been updated

Similar bugs occur on
* Product/Repositories page (where we add a repo to the product and the index still shows the previous number) 
* Content Views, where the repo/env names are not similartly update
* Gpg Keys with the product/repo count 
and so on. This is probably true for every nutupane page.

We need a generic mechanism/service to automatically update the Index list when we change specific details of one of the items

Created from redmine issue http://projects.theforeman.org/issues/6850

Upstream bug assigned to walden

Upstream bug component is WebUI

Per 6.3 planning, moving out non acked bugs to the backlog

This is an older bug, which is being tracked upstream. We will not be tracking this downstream. When the upstream issue is resolved, the next rebase will pull in the fix.