Bug 477019

Summary: Move User-Legacy Entitlement mappings from SEP to Issue-Tracker
Product: [Retired] Issue-Tracker Reporter: Mike Amburn <mamburn>
Component: AdministrationAssignee: Issue-Tracker Bug Watch List <issuetracker-bugs-watch>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: high    
Version: 4.7CC: gshipley
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-29 20:00:24 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:
Attachments:
Description Flags
Suggested implementation
none
Suggested implementation none

Description Mike Amburn 2008-12-18 17:51:21 UTC
Created attachment 327345 [details]
Suggested implementation

Background:
We need to move user-legacy entitlement mappings from SEP to Issue-Tracker to enable JBoss support technicians to manage those relationships without requiring an additional application/login.

Requested Change:
Add a new page attached to the user account page.
- link label: JBoss Legacy Entitlements

Security:
Only users with "JBoss" admin level should see link or access new page.

Fields to be captured:
1. Legacy entitlement (drop down)
- values: list from db table, format:  [ID]: [NAME]
2. Support Level (drop down)
- values: None, Bronze, Silver, Gold, Platinum, Enterprise
3. Expiration date (text)

Suggested implementation is attached. Saving the screen will refresh the table with an empty line at the bottom each time.

Comment 1 Mike Amburn 2008-12-18 18:15:52 UTC
Created attachment 327350 [details]
Suggested implementation

Comment 2 Grant Shipley 2008-12-18 19:52:31 UTC
Moving to XPlanner backlog

Comment 3 Mike Amburn 2009-01-29 20:00:24 UTC
Moving legacy entitlements to Oracle; no need to add to Issue-tracker.