Bug 570618

Summary:	RFE: inform & enable users to self-educate via the beaker web-app. ,
Product:	[Retired] Beaker	Reporter:	Kevin Baker <kbaker>
Component:	web UI	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.5	CC:	bpeck, dcallagh, ebaak, ineilsen, kbaker, mcsontos, mishin, rmancy
Target Milestone:	future_maint	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	MC
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-07 07:23:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Baker 2010-03-04 21:19:11 UTC

This is a very high level request. Please don't take it as a literal implementation. What I'm looking for is a way to communicate with the user base via the application itself. Information that would be handy to communicate would be

1# User documentation. How To's, FAQ's
2# Communication channels, irc, mailing lists
3# Outage information, upcoming and historical
4# Title bar status information

Some information might be useful to have on every web page in a title bar. Perhaps if there is an upcoming outage or some other event like a lab controller gone down then the title bar could have a link to a full explanation. e.g. Title says "Boston Lab Controller Down - More Info".

Likewise the help tab should be on every page so users can get to documentation.

There should also be a splash page that could list interesting information. Like upcoming outages or what was upgraded as well as links to historical information. It'd be nice if the scheduler splash page could show a graph of the number of jobs scheduled over the last week per time unit and the number of recipes in queue per time unit.

Again, these are just suggestions to reduce the admin & training burden by enabling users to access the information from the application itself.

http://www.digital-web.com/articles/user_interface_design_for_web_applications/

Comment 1 Raymond Mancy 2012-04-10 00:36:13 UTC

Re:#3. The MOTD was an attempt in this direction. For the purpose of outages, known issues, and other succinct pieces of communication, it works reasonably well.

Comment 2 Min Shin 2012-11-07 07:23:11 UTC

This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.