User:Tstaake@worcester.edu

About Me
My name is TR, I am a Computer Science Major with a Math Minor. I am also an intern at Staples.com working on their Release Engineering team. If you wanna know more about me or what i do at work just ask!

Issue Tracking Response
Bug Reporting Definition:

T: Type - This is an icon identifying what type of ticket it is: New Feature, a Bug, a technical task, a task, a story

Key: This is the unique identifier that is assigned to each ticket so they can be uniquely referenced

Summary: A brief summary of what the ticket is about

P: Priority - This field indicates the severity of the bug or priority of a feature the values are: TBD, Could, Must, Should and Blocker TBD - Priority Status has yet to be assigned Could - Not a critical issue and can be worked on "as resources permit" Should - Issue should be completed for its milestone, however, will not delay the milestone. Must - This bug or feature is key to a milestone, it has helped define the milestone and the milestone may be delayed to address this issue Blocker - This issue is blocking development or testing causing it to come to a standstill until the issue is resolved

Status: Needs Assesment - Ticket needs to be assessed Waiting on information - Ticket is waiting on additional information or clarification by someone other than the person assigning the ticket Ready for Work - Ticket has been reviewed and is ready for assignment or to be claimed Closed - The issue has been resolved or addressed correctly and marked complete, closed issues are still able to be reopened

Assigee: The Person who has looked over the issue and is responsible for assigning it to an developer or other resource

Updated: Date the last update to the ticket was made

Resolution: In the resolution field it seems that bugs (errors in the code) and Changes (new features/ functionality) have different resolutions I will mark, bug change or both to indicate which is for which. Unresolved (both) - a solution has not been found this ticket. Information Provided (both) - Information was provided to resolve the issue to the person who submitted the ticket Fixed (bug) - Issue has been addressed and fixed Won't Fix (bug) - Issue will not be fixed Change Request Cancelled (change) - Change requested does not need to be addressed Change Implemented (change) - Change requested has been implemented Cannot Reproduce (bug)- Unable to reproduce the issue that lead to the bug.

Due: Date the ticket needs to be resolved by

Reporter: Name of person submitting the ticket.

Created: Date the ticket was created

I found what these categories meant by hovering over them to see if any information would pop up there. Then I would scan through the list of tickets to see what the different options showing up were. Some of the things are self explanatory and some of them I was able to figure out by piecing to gather things I have heard at work and seen in this class so far.

When I first came to the site the tickets were displayed sorted by ticket number, to me i would have thought they would be sorted by priority with the highest priorities at the top.

The Symbols under priority just indicate the severity of the issue. as detailed above

Looking at ticket XFRM-174, the bug was submitted on 12-05-13 and there has been no recent discussion about it. This is a current issue but has been unassigned. The issue seems to be that when you switch to a group box any data that has been entered disappears. I'm not 100% sure how I would fix this, if the switch takes place via a method call then you would need to pass all the data that is in the form to the new method, but that seems expensive, since all the fields seem to stay the same I would think about just changing the logic of how the information is sent, using polymorphism to send the appropriate information at the end and not having to re-load the page for different things that seem to use the same form.

Project Info
When looking at the projects info i found the following:

1) The lead on the project is: Daniel Kayiwa

2) In the last 30 days one issue was created and 0 were resolved

3) Status Summary: This module serves as one of the alternatives to Microsoft InfoPath for OpenMRS data entry. The module converts an OpenMRS form to an XForm. Data entry can be done using any browser that supports JavaScript. The browser which has been tested most frequently with this module is Mozilla Firefox and hence is the recommended.

4)   XForms Module:   Version: 4.0.9.5   # of Issues: 0    # of Resolved Issues: 1

5) The most popular issue is: XFRM-163	Integrate UUIDs in xforms structure

6) The most popular label is: ampath

7) There were no associate builds found.