Bug 139044

Summary:	RHN purchase history very very confusing.
Product:	Red Hat Satellite 5	Reporter:	manoj <bhatiam>
Component:	Other	Assignee:	Todd Sanders <tsanders>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	cpelland
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-24 18:07:06 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 manoj 2004-11-12 18:31:03 UTC

Description of problem: When you look at the RHN purchase history, it
is very difficult to tell what is active and what is not. If you look
into any account(RHN login mis), there is no way to figure
out what is going on. I can tell when a subscription starts and ends.
But there are renewals which throw me off completely. Also when there
is something up for renewal(or has been renewed), the dates are messed
up till the contract goes live. 


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


How reproducible:Here are a few suggesstions.


Steps to Reproduce:
1.Like the Easy ISO', make a 'Relevent' and 'ALL'. Relevent showing
only active contracts and All showing active and inactive.
2.Add another column showing 'Y' active, 'N' inactive 'R'for renewed
or up for renewal
3. Take out Phone support & websupport link ( or make a welink when
you click on the contract, that shows what is the phone and websupport
avaiable.  
4. Since the purchase table is taken from CRM, please include product
keys registered by customers. They will have an idea when the when the
number was registerd. 
5. 
Use this format instead what we have. Also when people get management
they get an update service. Customers think the update can be used on
another account, and the end up registering systems to no base
channel. Can clarify this situation

As reported by system groups:
Entitlement Type 	Slots Total 	Slots Used
Update Service 	        3 	         0
Management Service 	6 	         0

  
Actual results:


Expected results:


Additional info: