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:
Not sure if I understood it correctly but I found a weird behaviour with audit comments. 

I created a template and updated some comments under "audit comments". Later when I selected the same template to see comments under 'audit comment' the testarea was blank.

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

How reproducible:
always

Steps to Reproduce:
1. create a template with audit comments
2. after creating the template, select it again and check for audit comments given while creating the temp.
3.

Actual results:
the textarea for audit comments will be blank

Expected results:
It should show the comments after template creation.

Additional info:

Audit comments are stored under Monitor>Audits and on the "History" tab when editing the template again.  The text box isn't meant to be repopulated.

Please confirm, but this appears to be NOTABUG.

Per triage, issue closed.  the textarea is meant to be an input for changes, not a definitive history itself.  That is stored/displayed elsewhere.