User:Nzelaya@worcester.edu

Intro
My name is Natalie Zelaya, I'm a Computer Science student here at Worcester State. Blog: http://natyzelaya.wordpress.com/ OpenMRS ID: nataliezelaya GitHub: NatalieZelaya

Part 1 - Bug Reports
1.	Issue Type: Used to organize issues into categories.

2.	Key: Assigns an unique identification number to each bug reported.

3.	Summary: A brief description of the issue.

4.	Priority: Sort issues depending on their priority level or status.

5.	Status: Shows the availability to work on each bug.

6.	Assignee: Displays the person who is currently working on the bug.

7.	Updated: Records each modification made to the issue.

8.	Resolution: Keep track of any final solution or the status to an specific issue.

9.	Due: The date when the issue needs to be completed.

10.	Reporter: Person who reported the issue.

11.	Created: Date when the bug report is created.

3.	Describe how you discovered the definitions and How did you find the information from above? The column names are pretty self-explanatory. By doing different searches, you'll see how the columns are being populated.

4.	Identify the order in which the bugs are initially displayed? The bugs are displayed sorted by key descending

5.	What is the meaning of the symbols under priority? The symbols means the level of priority for each bug; e.g. top or low priority. Also, depending on which symbol is being used it means the status; e.g. if the priority has not been established, or has been blocked.

6.     The bug that I looked at was ITSM-2842. The bug was submitted on Nov. 03, 2012 15:10:17 EDT by Burke Mamlin. There have been some interesting comments about this bug and the latest update was Nov. 06, 2012. The bug is currently open, and has been assigned to IT On-Call. One of the solutions presented and that I would like to work on is to create a custom 404 page to fix the bug.

Part 2 – Project Information
Burke Mamlin
 * 1) Who is the lead on the project?

34 created and 23 resolved
 * 1) In the last 30 days, how many issues have been created and how many have been resolved?

In Progress 46, 1% Reopened 2 Closed 3212, 81% Waiting on Information 7 Ready for Work 491 12% Code Review (Pre-Commit) 10 Code Review (Initial)	10 Code Review (Post-Commit) 78, 2% Design 87, 2% Needs Assessment 26, 1%
 * 1) Copy and paste the status summary.

4. Pick a version and note the version, the total number of issues, and the number of issues resolved. Order Entry Sprintt 1: Version release date 07-03-2011. 28 of 35 issues have been resolved

5. What is the most popular issue? TRUNK-1 and TRUNK-2069

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? Most recent build: Demo - Deploy Nightly Demo #33 (17 Feb 2014, 3:32:21 AM) Duration: 2 minutes Test: No tests found