From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
As discussed the following changes are required on the RHN site specific to
customer service. When folks send emails to customer service there is no
customer number or login information. Appreciate if either one or both is
included so CS can pull the entitlement information easily.
Secondly, the RHN payment page needs the following changes. This is
critical because we can start the customer without waiting for his/her
payment. Appreciate if both changes can be included in the next RHN push.
To purchase RHN entitlements, you may also mail a check or money order to us
using the following address...
PO Box 951701
Dallas, TX 75395-1701
If you are mailing in payment for your RHN Entitlement purchase, be sure to also
email your order details to firstname.lastname@example.org. Your email should include
your check number, the total amount of payment, type and quantity of
entitlement(s) desired, and the Red Hat Username you will be using to manage
your entitlements. Failure to send an email containing this information may
result in a delay of your RHN Entitlement service activation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Both changes in CVS: The first request involved changing the message template to
include the user login, and oracle customer number (if any).
In the second request, '*LOCKBOX*' doesn't look right to me there, but I put it
in verbatim. e-mail sent to narsis requesting confirmation.
The change also affects the message body for 'regular' feedback sent from
/help/contact.pxt, as the code is the same.
The first change isn't customer-visable. The second change is visible in the
reworded text at /network/sales/index.pxt
User Login: jkomenda
User ID: 2011903
Customer Number: None
What is 'Customer Number' supposed to be?
The oracle customer number - web_customer.oracle_customer_number in our schema.
No idea what it's used for - our side of the codebase doesn't use it at all.
Narsi asked for it, so I put it in....
Ok, looks good in dev.
Looks good in QA.
Looks good in prod.