
Monday, May 4, 2009
Sunday, April 20, 2008
Thursday, April 17, 2008
Finally the application link is up!!
check it out at http://chabo.itmill.com/
So stay tuned to see the power of ITMILL toolkit 5.
Tuesday, March 4, 2008
User interface, New screen shots

After the second meeting with our customer, we aggreed on changing the user interface, not the look but, the way it was operating. Before we had all components rendered on the same parent window. Which had some limitations to the way the application is supposed to funtion as an emmbeded application.
Here are some screen shots of new window forms.
List of ticket window.
This window shows all the tickets available in the database.

After searching for a ticket, this is a search result window.

When a ticket has been selected, this window shows all the ticket details.

This is the window used to create new ticket to the ticket database.

Window used for adding attachments to the ticket.

Thursday, February 28, 2008
Second Project meeting
So far so good, we got to solve some critical problems with the help of some ITmill specialists and now everything is back on trac an we are rolling on with few remaining stuffs.
stay in touch.
Monday, February 25, 2008
CLASS DESCRIPTIONS
The description of the Ticket
Class name | Ticket | |
Specification | A class that defines a collection of attributes that makes a ticket. Ticket is a term used in internet support to submit a problem specification. | |
Super Class | No super class | |
Attributes | id | An identification number of a ticket |
type | type of the ticket, if it is a defect, enhancement or task | |
time | this shows when the ticket was created to the system | |
changetime | this shows the most current time when the last comment was posted, or attachement | |
component | In this case this shows which component is concerned in a ticket | |
severity | this describes how critical is the problem | |
priority | this describes how is the priority of the ticket | |
owner | this is the name of the person who will be responsible for the ticket | |
reporter | name of the person who creates a ticket | |
cc | Carbon copy to someone else than owner | |
version | version of the system reported | |
milestone | this denotes how far the issue has been resolved | |
status | Shows the stage process of the ticket issue. | |
resolution | Like status but shows that the ticket is valid, a duplicate or fixed. | |
summary | Short title of the ticket. | |
description | Short explanation of the ticket. | |
Keywords | this are map words to be used for indexing or searching tickets | |
Associations | No associations | |
The description of the TicketAttachment
Class name | TicketAttachment | |
Specification | This is an extra file which is added to the ticket as a supporting document or a reference. it can be any type of document file in electronic form. | |
Super Class | No super class | |
Attributes | type | This defines to what is the attachment attached to. e.g. ticket or wiki |
id | identification number of the attachment | |
filename | This is a name of the attachment. | |
size | size of the attachment in bytes | |
time | The time an attachment has been added. | |
description | short summary about the attachment | |
author | the name of the person who added an attachment | |
ipnr | ip number | |
Associations | No associations |
The description of the TicketComment
Class name | TicketComment | |
Specification | Test description added as extra information to the ticket, it can be an advice, or criticism. | |
Super Class | No super class | |
Attributes | ticketId | unique identification of a comment |
createTime | The time when the comment was added. | |
owner | This is the name of the person who will be responsible for the ticket. | |
content | The text content of the comment. | |
Associations | No associations |