Bug 477019 - Move User-Legacy Entitlement mappings from SEP to Issue-Tracker
Summary: Move User-Legacy Entitlement mappings from SEP to Issue-Tracker
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: Administration
Version: 4.7
Hardware: All
OS: All
high
low
Target Milestone: ---
Assignee: Issue-Tracker Bug Watch List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-18 17:51 UTC by Mike Amburn
Modified: 2009-01-29 20:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-29 20:00:24 UTC
Embargoed:


Attachments (Terms of Use)
Suggested implementation (943 bytes, application/octet-stream)
2008-12-18 17:51 UTC, Mike Amburn
no flags Details
Suggested implementation (21.43 KB, image/png)
2008-12-18 18:15 UTC, Mike Amburn
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.