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.
Description of problem: Changeset history does not list who promoted a changeset, yet the information is readily available.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Changeset history page
2.
3.
Actual results:
No author/promoter information.
Expected results:
Promoter visible.
Additional info:
Changeset.first.task_status.user ???
Todd,
When you say 'logged' history, what do you mean exactly?
Will it be in a log file?
Will it show up in the organization history?
I'm not sure exactly what you mean.
-Justin
Adding to changeset history page:
7993971daf93709c19127f2aff2442b483306402
Adding to search index for changesets:
6cf694b4cf06b9a85811d7c4ae60adc6108833df