Bug 1994886

Summary:	[RFE] Add Description column to explain the purpose of Default Report Templates shipped with Satellite 6.10
Product:	Red Hat Satellite	Reporter:	Sayan Das <saydas>
Component:	Reporting	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	ahumbe, dsinglet, mhulan, sajha, wpinheir
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 01:02:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sayan Das 2021-08-18 05:58:48 UTC

Description of problem:

In every new release of Satellite 6 we introduce one or two new report templates but we don't document their use cases anywhere. For customer's it could be confusing as they don't know what template to use for what kind of data unless someone decides to look into code or run it against some hosts.


The idea is to have a "Description" Field" added in Monitor --> Report Templates page to give a basic descripion of what that template can be used for.

And the request is for all these templates for now.

Ansible - Ansible Inventory          
Host - Applicable Errata             
Host - Applied Errata                
Host - compare content hosts packages
Host - Last Checkin                  
Host - Registered Content Hosts      
Host - Statuses                      
Host - Vulnerabilities               
Jobs - Invocation report template    
Subscription - Entitlement Report    
Subscription - General Report        
User - Registered Users


Also if someone is creating a new template, they should be able to set their own custom Description and modify the same if needed.


Version-Release number of selected component (if applicable): Satellite-6.10

Satellite 6.10


Additional Information:

A documentation BZ has been filed as well for a similar purpose i.e. https://bugzilla.redhat.com/show_bug.cgi?id=1994884

Comment 3 Brad Buckingham 2022-09-02 20:25:18 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 4 Brad Buckingham 2022-09-05 22:55:19 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Eric Helms 2024-06-06 01:02:03 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.