User:Swapna25

Depending on whether the Task/Feature/Bug/Test is related to a specific application or to Reader, a new ticket has to be created in Redmine. Once a new ticket has been created,the following fields that appear in the ticket need to be described in a clear manner:

Tracker

 * Task    :    If any
 * Feature: If an application requires a particular feature to be added to it in order to improve its functionality,appearance or usability, a feature request has to be made.
 * Bug     : If the QA Technician finds any problem/bug with the application that affects its performance and makes it  malfunction/buggy, then a Bug report has to be made.
 * Test    : If a particular application has to be tested( Regression or Release), then a release ticket needs to be assigned to the concerned person.

Subject
The subject of the ticket has to be clear, descriptive and to the point.It should be directly related to the ticket and be self-explanatory. To get a better understanding of how to write the ticket subject, it is recommended to read Subject

Below, you can find a detailed explanation regrading ticket subject description w.r.t the selected 'Tracker'(Task/Feature/Bug/Test): For a Task ticket, the task that needs to be implemented has to be mentioned.It should not be verbose, and has to simply mentioned the desired task that needs to be done.

Below are a few task ticket subjects: For a Feature request ticket, only the feature that needs to be implemented has to be mentioned in the subject and not the reasons behind the request.
 * 1) Merge and tag 1.9.0
 * 2) Build Palm 1.5.0

Below are a few examples of Feature ticket subjects( The titles are self-explanatory):
 * 1) Create the default jumpto icon for iPhone
 * 2) Darker font color for the Index Search Bar
 * 3) Suggestion: Make application's font use system's font
 * 4) Change link name to Tarascon Pocket Pharmacopoeia/Tarascon

A not so ideal way of describing tickets, is to make the title generic and not clear to the developer(who is in charge of implementing the feature)For example,if the Ticket #2 was described as "Change font color"/" Darker Font Color"/"Search bar text not clear", then the subject remains vague and not to the point. A preferable way of doing this, is to simply describe the feature and the place it has to be implemented in. For a bug ticket, the title needs to clearly describe the bug, i.e, unusual actions that are taking place or features that are not working correctly in the application or any problem that the QA Technician feels is affecting the normal operation/use of the application. The title has to be concise and specific.

For example, if a bug has been found where images on a BB touch-screen device do not zoom in, then:

"Images do not fit to screen" or " Fit to screen feature not working correctly" is a very generic way of describing a ticket and is not recommended. Images does not fit to screen when the user taps the 'view whole image' button" is a much better way of describing the bug The following are a few examples of bug ticket titles:
 * 1) Highlighted index entries do not lead to pages
 * 2) Index entry missing link
 * 3) Tools tab not highlighted on selection

For a Test Ticket, only the platform for which the application has to be tested has to be mentioned in the title. Below are a few examples of Test ticket subjects:


 * 1) BB Test
 * 2) Phone Test

Description
This section requires an adequate description of a feature/bug/test/task ticket. The application along with the build used to test should also be mentioned in the description.The description should contain the reasons behind the ticket and suggestions if applicable.Below, you can find a detailed explanation regrading ticket description w.r.t the selected 'Tracker'(Task/Feature/Bug/Test): For a Task Ticket, the ticket should contain a brief description of the task that needs to be done. Below are a few examples of Task Ticket descriptions:


 * 1) Please provide a TRSC palm build (non reader), with security turned off. No installer necessary.
 * 2) Please merge trunk with BB 1.9.0.

For a Feature Ticket, the ticket should contain a description of the feature(s) that need to be implemented,along with reasons behind the feature request. Below are a few examples of Feature ticket descriptions:


 * 1) Please create the default jumpto icon for iPhone
 * 2) For FIRSTAID BlackBerry_1.9.0_9,when the user goes to the Index and types in the Index Search bar, the font of the text entered appears very light, as it is almost the same color as the search bar. As such, it is tough to read the characters clearly. It is preferable to have a darker,more visible font color than it is at present.
 * 3) Users are complaining that the font size used in Tarascon Pharmacopoeia is too small too read, and that they are unable to change the font size in the application. It would be useful that the application used the phone's system font, this way users could change the size depending on their needs.

For a Bug Ticket, the ticket should contain a description of the bug(s) found in the application along with steps on how to reproduce them. Below are a few examples of Bug Ticket descriptions:


 * 1. For THMP BlackBerry_1.9.0_7/TAEP BlackBerry_1.9.0_14 application(s) on non-touchscreen devices:

Index->Index search->anemia An entry titled "anemia" is highlighted in the Index Clicking on the "" entry does not lead to a page. Instead,you need to scroll down to the next entry,"anesthesia" and then scroll up again to "anemia",to view the page This is the case with all the index entries
 * 2. In ACSE BlackBerry_1.9.0_6, the below index entry is not linked to any page

Index->GFR->Empty
 * 3. In RHEUM Palm_1.5.1_3,if you click on the Tools icon, the tools page is displayed correctly but the tools tab is not highlighted.To reproduce this:

Click on the Index icon,the Index tab is highlighted Now,click on the Tools icon, the tools tab does not get highlighted and instead the Index tab remains highlighted

For a Test Ticket, the ticket should simply mention the test that needs to be done and the application that needs to be tested. Below are a few examples of Test Ticket descriptions:


 * 1) Please make an release test for Blackberry.
 * 2) Test iPhone release. Hudson is set up.

Status

 * New - A new ticket will be created.
 * Resolved - The issue related to the ticket has been resolved.
 * Feedback - The developer/tester has worked on the ticket and wants to share further information regarding the ticket.
 * Closed - The ticket has been closed.
 * Rejected

Start
Leave Blank

Priority
This field needs to be chosen depending upon the urgency and requirement involved in the development/testing/release of the application.


 * Low- The ticket assumes low importance/priority compared to others
 * Normal- The ticket has the same importance as others in this category
 * High- The ticket precedes other tickets(marked low and normal) in priority and should be resolved before them
 * Immediate- The ticket is of the utmost priority and needs to be completed immediately

Assigned To
The person who created the ticket has to assign it to the concerned person

Target Milestone
The correct milestone related to the application/Reader needs to be chose. Example:Blackberry 1.9.0/iPhone 1.9.0/

Due date, Estimated hours
Leave Blank

Done
The % task done needs to be filled in