WikiStart > Documentation > Tickets and The Roadmap

Tickets and The Roadmap

  1. Tickets and The Roadmap
    1. What Are Tickets
    2. Projects In Beaversource
      1. The Roadmap
      2. Tickets
    3. Writing A Ticket

What Are Tickets

Tickets in Beaversource represent issues within a project that need to be addressed. There are three types of Tickets: Defects, Enhancements and Tasks. They can be ideas that other members of the project may want to pursue or small goals within a milestone. For instance, a Beaversource Admin project member realized that documentation was needed to assist users in understanding Beaversource's function. A new Milestone was created and Tickets were composed to focus the implementation of documentation. See below

As you can see, these Tickets are Enhancements and Tasks.


Projects In Beaversource

To access tickets in Beaversource, you must be a member of a Project. To foster an environment of sharing, learning, and contribution amongst OSU students and programmers, Beaversource provides the following resources for your project(s):

  • Version Control (Subversion)
  • Project Wiki (Trac)
  • Bug tracking/Ticketing (also Trac)
  • Social Network (Elgg, in development)

After heading to your project's webpage, you will notice that you have access to new tabs: Roadmap and Tickets.


The Roadmap

The 'Roadmap' provides a view on the ticket system that helps planning and managing the future development of a project. The 'Roadmap' is a list of future milestones. Each milestone contains a description (using WikiFormatting) describing main objectives and other goals. In addition, the tickets targeted for a milestone are aggregated, and the ratio between active and resolved tickets is displayed as a milestone progress bar.


Tickets

The Tickets tab in Beaversource reports the active tickets in your project. 'Active' tickets are bugs or issues within the project that have not been resolved. The report shows the Ticket #, Component, Version, Milestone, Type, Owner and Date of creation. For more information see TracReports.


Writing A Ticket


1. To write a ticket, go to your project's website (usually: http://beaversource.oregonstate.edu/projects/[project name]) and click the Tickets tab.


2. Next, click the Create new ticket button.


A ticket contains the following information attributes:

  • Reporter - The author of the ticket.
  • Summary - A brief description summarizing the problem or issue.
  • Description - The body of the ticket. A good description should be specific, descriptive and to the point.
  • Type - The nature of the ticket (for example, defect or enhancement request)
  • Component - The project module or subsystem this ticket concerns.
  • Version - Version of the project that this ticket pertains to.
  • Keywords - Keywords that a ticket is marked with. Useful for searching and report generation.
  • Priority - The importance of this issue, ranging from trivial to blocker.
  • Milestone - When this issue should be resolved at the latest.
  • Assigned to/Owner - Principal person responsible for handling the issue.
  • Cc - A list of other associated people. Note that this does not imply responsibility or any other policy.
3. Fill out the new ticket with as much detail as possible. The goal is to be as precise and accurate as possible so the issue can be understood. Also, make sure to select defect, enhancement or policy from the 'type' drop-down field. Then, Click Submit ticket.

Attachments