Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 976888 - String Update: 'Support Level' and 'Support Type' -> 'Service Level/Type'
Summary: String Update: 'Support Level' and 'Support Type' -> 'Service Level/Type'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: sam20-tracker
TreeView+ depends on / blocked
 
Reported: 2013-06-21 18:53 UTC by Matt Reid
Modified: 2014-03-18 17:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 17:37:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Sat6 Details pane (48.83 KB, image/png)
2013-06-21 18:54 UTC, Matt Reid
no flags Details
Portal System Details, shows some subscription info (51.04 KB, image/png)
2013-06-21 18:55 UTC, Matt Reid
no flags Details
One of Subscription manager's displays (20.87 KB, image/png)
2013-06-21 18:56 UTC, Matt Reid
no flags Details

Description Matt Reid 2013-06-21 18:53:08 UTC
Description of problem:
We currently say Support Level and Support Type in the Subscription Details pane in SAM/Satellite6. We call those Service Level and Service Type in Customer Portal and in Subscription Manager. 

For example, if you use rct cat-cert on an entitlement cert:

+-------------------------------------------+
	Entitlement Certificate
+-------------------------------------------+

<snip>

Order:
Name: CloudForms Employee Subscription
Number: 40019540
SKU: SER0412
Contract: 10100142
Account: 1460290
Service Level: None
Service Type: None
Quantity: 1

<snip>


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

How reproducible:
100%

Steps to Reproduce:
1. Log into Sat6
2. Navigate to Subscriptions (I think it's Content > Red Hat Subscriptions or Subscriptions)
3. Click on a subscription to see the details pane/Subscription Info

Actual results:
Service Level/Type is listed as Support Level/Type

Expected results:
Service Level/Type to be consistent with other tooling

Additional info:

Comment 1 Matt Reid 2013-06-21 18:54:37 UTC
Created attachment 763937 [details]
Sat6 Details pane

Comment 2 Matt Reid 2013-06-21 18:55:16 UTC
Created attachment 763938 [details]
Portal System Details, shows some subscription info

Comment 3 Matt Reid 2013-06-21 18:56:00 UTC
Created attachment 763939 [details]
One of Subscription manager's displays

Comment 4 RHEL Program Management 2013-09-17 04:25:17 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 7 Mike McCune 2014-03-18 17:37:33 UTC
This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.


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