1. Proposed title of this feature request  
    Add an "Upgrade Satellite" button or link on Satellite 6 Web UI that points user to upgrade process/instructions, and ideally starts the upgrade if possible. 
      
    2. Who is the customer behind the request?  
    No a request from specific customer, more of a lesson learnt from Satellite 5 over the years to make the upgrade instructions more visible to customers.  For Satellite 5, upgrade instructions are provided in rhn-upgrade package, and even though it's highlighted in documentation and kbase content, many customers still don't find/read it (some assume yum update will do the upgrade).  Integrating it in the UI will make it much more prominent to customers since it's visible as part of using the Satellite day-to-day, reducing unnecessary upgrade pains (and support load).
  
    3. What is the nature and description of the request?  
    Please see above.
      
    4. Why does the customer need this? (List the business requirements here)  
      
    5. How would the customer like to achieve this? (List the functional requirements here)    
    Add an "Upgrade Satellite" button or link on Satellite 6 Web UI that points user to upgrade process/instructions, and ideally starts the upgrade if possible.  
    Suggestion: detect the Satellite version / update level and offer options - for example ask if customer is trying to upgrade from 6.1 to 6.2, or update from 6.1.1 to 6.1.2 <-- this would also solve the problem of customers not reading update steps in errata text and yum update unable to do all the Satellite specific steps.
    But if that takes a long time the quick win is just a prominent link that points to upgrade docs.

    6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
      
    7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
      
    8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
      
    9. Is the sales team involved in this request and do they have any additional input?  
      
    10. List any affected packages or components.  
      
    11. Would the customer be able to assist in testing this functionality if implemented?