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.

As a User, I need to have a better graphical status on the overall health of the tasks.

A Task page that includes a Dashboard with an emphasis on the Paused tasks and tasks with Errors/Warnings.

Checked in Sat 6.6 snap 10, issues reported previously in upstream still persist,

- https://projects.theforeman.org/issues/27078 -- I find this a blocker for this feature
- https://projects.theforeman.org/issues/27081 -- I'd like as much as possible of these notes tackled to reduce user confusion from the new feature

Cheers

I have added `react-router-bootstrap` to the new `vendor` project to reduce the chance it will happen for the next versions:
https://github.com/theforeman/foreman-js/blob/master/packages/vendor-core/package.json

Let me know if there are other packages you want to add there.

Verified on satellite 6.6 snap 23. The desired functionality is there, the majority of associated bzs has been fixed, the remaining I consider non-blocking for the release

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.

https://access.redhat.com/errata/RHSA-2019:3172