User:Janaya@worcester.edu

My name is Jesse Anaya. I am a senior at Worcester State University majoring in Computer Science.

I like to work with computer hardware and love to build custom PC's. I enjoy snowboarding in the Winter and skateboarding and soccer in the Summer.

You can follow my blog at:

Part 1 - Bug Reports
Define the purpose of the column names below. Include the range of possible values for 4, 5, and 8 below.

1. Issue Type
 * Whether an issue is something technical, a general task that needs completion, a bug, feature, enhancement, etc.

2. Key
 * A reference number to a specific ticket or submission. The key also preps the board members on what it may contain with a prefix.

3. Summary
 * A general summation of the ticket.

4. Priority
 * The attention a ticket needs; values include: Any, Blocker, Must, Should, Could, Non-Essential, TBD

5. Status
 * The current status of the ticket and whether or not it is in a holding period; values include: Any, Open, In Progress, Reopened, Resolved, Closed, etc.

6. Assignee
 * Which user is assigned to contribute to the ticket

7. Updated
 * The last time a modification to the ticket was made

8. Resolution
 * The closing status of the ticket; values include: Unresolved Fixed, Won't Fix, Duplicate, Incomplete, etc.

9. Due
 * When the ticket must be finished by

10. Reporter
 * User or group who submitted the ticket

11. Created
 * The date the ticket was created

Describe how you discovered the definitions and How did you find the information from above?
 * I found all definitions and info by visiting the Issue Navigator and inspecting the left hand category filters.

Identify the order in which the bugs are initially displayed?
 * The default order of the bugs is by date created and by key as a sub sort.

What is the meaning of the symbols under priority?
 * Each symbol represents the priority. For instance, a red up arrow signifies that the "issue should be completed by its milestone, but will not delay the milestone." A question mark means that there is no priority yet, "TBD", among others.

Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
 * XFRM-159

Identify when the bug was submitted.
 * Bug was submitted on 5/8/2013.

Identify if there has been recent discussion about the bug.
 * There are no comments on the issue.

Is the bug current?
 * The bug is still current and affects users using IE 8.

'''Is the bug assigned? To whom?'''
 * The bug is currently unassigned.

Describe what you would need to do to fix the bug.
 * I would first look at the browser check in the code and see if it has any sort of check for compatibility for older browsers (IE 6/7/8, Firefox 3.6, Chrome Beta, etc.) and see if adding the additional browser versions would work.

Repeat the previous step with a different kind of bug.
 * XFRM-89. This bug also deals with a browser issue where Chrome does not create a form correctly and returns a null pointer exception once adding a patient. It was created on 7/18/2012. There are only 2 comments posted from July 2012 but the bug still is current and unresolved. The ticket is assigned to nobody at the moment. I would investigate the given XML code as well as the source code attached to the web form and see where the pointer might be referencing. It would appear that it is not affected by browser version.

Part 2 - Project Information
1. Who is the lead on the project?
 * Burke Mamlin is the lead on the project.

2. In the last 30 days, how many issues have been created and how many have been resolved?
 * In the last 30 days, 31 issues were created and 19 were resolved.

3. Status Summary In Progress 47 1% Reopened 2 Closed 3215 81% Waiting on Information 8 Ready for Work 476 12% Code Review (Pre-Commit) 10 Code Review (Initial) 25 1% Approved 1 Code Review (Post-Commit) 78 2% Design 87 2% Needs Assessment 27 1%

4. Pick a version and note the version, the total number of issues, and the number of issues resolved.
 * Version = OpenMRS 1.9.7
 * Total # of Issues = 10
 * Number of Issues Resolved = 7

5. What is the most popular issue?
 * "TRUNK-1	Limited number of trees in the world"

6. What is the most popular label?
 * "INTRO"

7. When was the most recent build, why was it run, what was the duration, and how many tests passed?
 * OpenMRS Core 1.10.x ran 5 days ago, it was ran because "Code changes detected", duration was "9 minutes", and tests were "1 of 2491 failed".