User:Dnatsis@worcester.edu

Dhimitris Natsis
I am a Student and a Computer Science Major at WSU.

My blog is. OpenMRS ID: dnatsis Github username: dnatsis

Issue Tracker activity

Issue Type - a category in the issue tracker which describes what kind of issue it is such as if it is a bug or maybe a new feature or an improvement and so on.

Key - this is the ticket number or how you would reference a specific issue, also the first part of the key identifies what kind of issue it is. For example keys starting with XFRM- followed by a number seem to be problems with XForm.

Summary - just a short description of the issue

Priority – a category that prioritizes the issues, since some issues might be a lot more important than others and need to be prioritized that way.

Status – Which part of the Debug Cycle the current issue is on.

Assignee – shows if a specific person has been assigned to work on that issue and if so their name.

Updated – shows the last time that the issue was updated.

Resolution – shows if an issue is resolved or not or if there is some other type of resolution such as the problem not fixing or not being reproduce the issue.

Due - a date in which a solution to the issue should be implemented.

Reporter – the person who first reported the issue.

Created – the date the issue was created.

The information above seemed pretty straight forward there was nothing too surprising in the issue tracker system. I figured out the definitions above by just using the issue tracker a little bit and by reading the fields under each definition. Initially the bugs in the issue tracker are displayed by key in alphabetical order starting from the end, issues of the same key type are then sorted by date with the most recent coming up first.

The symbols under the priority column represent what priority that issue is, such as must, should,could,blocker,etc.