SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 32 | Next

David J Murphy

"Managing Software Development with Trac and Subversion"

All aspects of the ticket can be edited and/or
amended while it is active, but keeping with the version control theme all changes
are tracked within a ticket so we can see what was changed and by whom.
Fields
Each ticket contains the following properties:
Reporter: The name or (more likely) email address of the person who created
the ticket.
Type: The nature of the ticket (e.g. reporting a defect or requesting
an enhancement).
Component: The project module this ticket concerns.
Version: The version of the project that this ticket is associated with.
Keywords: Keywords that a ticket is marked with. Useful for searching and
report generation.
Priority: The importance of this ticket.
Milestone: The release this ticket needs to be completed for.
Owner: Person responsible for progressing the issue.
Cc: A comma-separated list of other users or email addresses to notify. Note
that this does not imply responsibility or any other policy.
Resolution: Summarizes why ticket was closed.
Status: The current status of the ticket.
Summary: A brief description of the issue.
Description: The body of the ticket, detailing what the ticket has been
created for.
Roadmap
An extension of the tickets module, the roadmap provides a view of the ticket system
that aids in planning and managing the future development of the project.


Pages:
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44