User:Ckelley6@worcester.edu

My name is Connor Kelley. I am a computer science major at WSU.

Bug Tracker Exercise
An issue type is the type of issue that is found, and that the bug is being written about. This gives the project manager a basis for who to assign it to.

The key is a code number generated at the time of filing for the bug. It can be used to find the bug later on.

A summary is a short meaningful description of the problem that is shown in the search results field.

A priority is used in order to help decide the order in which bugs are addressed. This is decided based on the significance of the bug to the program.

The status of a bug indicates the current state of the issue. A bug that is set to open is ready to be touched, versus resolved, which is complete, versus a bug that is new, which hasn't been touched yet.

The assignee is the person or group that the bug is assigned to.

The updated category is the last time that someone touched the bug. This is useful to see the status aside from whether is is open, in progress, etc.

The resolution is the state in which the bug is finally left, and usually contains a reason for why the bug was resolved the way it was.

The due date is the requested date in which the bug is supposed to be completed.

The reporter is the person who originally filed the bug report.

The created section is the time and date that the bug was originally filed.

- 3 -

I found these definitions with a combination of previous knowlege for the basics, and the help buttons on the side of the search field for the specifics.

- 4 - The bugs are displayed by the key number according to open bugs, which is indicitive of when they were written.

- 5 - The symbols under priority indicate the priority of the bug. There is a table that breaks them down into meaningful names under the help section on the search.

- 6 - The bug that I looked at was XFRM-172. The bug was submitted on 2013-11-18 01:57:25 EST The bug is not current, it is closed. It was assigned to Daniel Kayiwa. I would most likely convert the information to lowercase when it get read in, so everything would match.

- 7 - The bug is XFRM-65 The bug was submitted on 2012-03-15 08:07:12 EDT The bug is open, and non-essential. It is currently unassigned. I might try and catch this exception and output a more intuitive error in the code, but there is probably more to it than that.

- Part Two - - 1 - The lead is Burke Mamlin

- 2 - In the last 30 days 40 bugs have been created and 24 have been resolved.

- 3 - https://tickets.openmrs.org/charts?filename=jfreechart-onetime-5746621184673836713.png

- 4 - v1.7.5 has 18 bugs, with 10 of them that are resolved.

- 5 - There is no most popular issue in this version

- 6 - I do not see where the most popular label section is

- 7 - The most recent build was run two days ago on 8 Feb 2014. It was a nightly CI build, not tests were run, and it took one minute