<!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:"Arial Black"; panose-1:2 11 10 4 2 1 2 2 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:647 0 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt;} h2 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:2; font-size:14.0pt; font-family:Arial; font-style:italic;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial;} p.MsoHeader, li.MsoHeader, div.MsoHeader {mso-style-name:"Header\,Even"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} p.MsoFooter, li.MsoFooter, div.MsoFooter {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {mso-ansi-font-size:9.0pt; mso-bidi-font-size:9.0pt; font-family:Arial; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-font-family:Arial; color:#333399; mso-text-animation:none; text-decoration:none; text-underline:none; text-decoration:none; text-line-through:none;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:723993499; mso-list-type:hybrid; mso-list-template-ids:-906055794 67698689 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:¿; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} @list l1 {mso-list-id:1679889067; mso-list-type:hybrid; mso-list-template-ids:-1539950382 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l1:level1 {mso-level-number-format:bullet; mso-level-text:¿; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} -->
h1. RT User Tutorial for SAP Support Pack 2008
Overview
RT is used to Open, Track and Report defects found during support pack testing. RT can be accessed via email or directly through the RT Self Service Interface.
h2. RT Email Access:
h3. +Step 1:++ + +Address an Email+
Using your preferred email application, (MSOutlook, MIT Webmail, Yahoo, Gmail...) paste the following address in the "To:" field; *saptest@help.mit.edu* When sent, this email address automatically creates a ticket in RT in the *SAP:: Test Issues* queue.
h3. +Step 2: Populate the Subject Line+
The subject line should contain the following \- SAP 2009
\- Functional Area
\- Summary of Ticket Example: *Subject:* _SAP 2009 - HR Payroll - Error on Distribution Changes posting data_
h3. +Step 3: Populate the email Body+
Details of the ticket are placed in the body of the email. Screenshots and/or attachments of screenshots should be included where available.
h3.
+Step 4: Receive Confirmation+
The sender receives an AutoReply email from *SAP Test Issues via RT (alias* saptest@RED-SOX.mit.edu *)* confirming the creation of the ticket. A link is provided in the body of the confirmation email to check the status of the ticket. Tickets created in the queue via email will be edited to ensure the correct Project Name (*SAP Support Pack 2008*) is assigned for future reporting.
h3. *{+}Step 5:+{*}{*}+ +* *{+}The Project Manager will set the following fields in RT:+*
* Environment
* Test Phase
* Issue Found In
* SAP Project Name
* Sub Area
* Company Code
* Severity
h2. RT Web Self Service Access
h3. +Launching RT+
RT can be accessed from MIT Web Self Service at the following link: https://help.mit.edu/SelfService/ This link opens the +RT for help.mit.edu+ interface and defaults to the user's open tickets (see Diagram 1). By clicking on the lines under the Subject header on any of these New Tickets you will launch the Update Window. Update Window functionality will be discussed in later steps. \\
h3. +Viewing Open Tickets+
To view Open Tickets, click on the "Open Tickets" menu option (Diagram 1). A list of the users open Tickets is presented.
h3. +Update Tickets+
Once a list of Open Tickets is presented on the screen, click on any line item under the Subject header to launch the Update Window (Diagram 2). The SAP Project Name field must contain the text "SAP Support Pack 2008" text. This text is used as a Project Identifier which allows SAISto discriminate between multiple projects using the "SAP:: Test Issues" RT Queue. Click on the "Update this Ticket" push button on the upper left corner of the screen. Users must press the "Submit" button at the bottom of the screen to save any changes to the Ticket. \\
h3. +Viewing Closed Tickets+
The users Closed Tickets are viewed by selecting "Closed tickets" from the menu options list on any screen. A list of the users Closed Tickets will appear on the screen (Diagram 3). As with the other screens, clicking on any line item under "Subject" will launch the Update Window (Diagram 2). Users must press the "Submit" button at the bottom of the screen to save any changes to the Ticket. \\
h3. +Creating New Tickets+
In order to create new tickets, select the "New ticket" menu option from any screen. This will launch the "RT Self Service / Create a ticket" screen (Diagram 4).
For this project we will use the "SAP:: Test Issues" Queue (Diagram 5). Click on "SAP:: Test Issues" to select this Queue. Selecting the Queue name from the list will launch the "RT Self Service / Create a ticket" Window (Diagram 6). This Window provides place holders for details regarding your defect. Providing details aids in defect resolution. Screen shots of defects or error messages can be attached to the ticket and are extremely helpful. The subject line is critical to identify this ticket as an SAP Support Pack related ticket. The *{+}subject line should contain the following:+* \- SAP 2009
\- Functional Area
\- Summary of Ticket Example: *Subject:*{_}SAP 2009 - HR Payroll - Error on Distribution Changes posting data_ Once all data fields are populated, click the "Create ticket" button on the bottom right of the screen. The user will receive an email from SAP Test Issues via RT (alias saptest@RED-SOX.mit.edu ) confirming the creation of the ticket. A link is provided in the body of the confirmation email to check the status of the ticket.
|