User:Tbruce@worcester.edu

= Hello! =

My name is Taylor Bruce

I am a Senior at WSU majoring in CS(Computer Science).

Here is a link to my blog: CLICK HERE

= Week 3 =

Part 1

 * Issue Type: Bug, new feature, epic, story, subtask, task. This tells users what the issue is for.


 * Key: TRUNK and the issue number related to it ex: TRUNK-4000


 * Summary: the 'summary' of the whole key or project


 * Priority: Blocker, Must, Should, Could, Non-Ess., TBD. How important this bug should be or how much attention it requires.


 * Status: In progress, reopened, closed, waiting on information, ready for work, code review pre-comm, code review initial, code review post, Approved, Design, needs assessment.


 * Assignee: Who the issue is assigned too


 * Updated: When the issue was last updated


 * Resolution: The status of the bug (either resolved or unresolved)


 * Due: Time the issue needs to be resolved by


 * Reporter: Who wrote up the issue


 * Created: Date the issue was created

I found the definition from viewing the main issue page https://tickets.openmrs.org/secure/IssueNavigator.jspa and seeing what the fields were populated with. I also used my knowledge from working as a Release Engineer to formulate the definitions.

The bugs are initially displayed in descending order of Key.

The symbols under priority stand for Blocker, Must, Should, Could, Non-Ess., TBD. THese symbols are used to quickly inform users the status of the issue.

Part 2
The project leader is Burke Mamlin. In the past 30 days of the OpenMRS project there have been 40 issues created and 26 resolved.

I chose OpenMRS version 1.11. There is a total of 284 issues for this version. With a total of 176 issues closed/resolved.

The most popular issue is TRUNK-2069 (Obs should have a pointer for the form_field it was created through) The most recent builds was 4 hours ago and it was kicked off due to a source change. It too 5 minutes to run and passed 2778 tests.