Student projects/Integrated bug tracker

Bug Tracker Module

System Features

• Use Moodle authentication and user accounts to login/report bugs/assign bugs/resolve bugs
• Display HTML/PHP/Javascript/other Web code without error
• Link related/dependent bugs and the status of related/dependent bugs
• View a particular bug as an external user (not logged in) using a simple URL (e.g. http://moodle.org/mod/tracker/view.php?issue=3455)
• All fields capable of using Moodle rich text editor as appropriate
• Subscribe/unsubscribe to receive bug emails
• Generate bug reports by user/severity/build/status
  • Generate Release Notes
• Create and save common reports/queries

System Development Lifecycle

Design

Pages

• Report a Bug Page
  • Allow users to report a bug
  • Requires that users be logged in to report a bug
• View Page
  • Browse
    • Allow users to browse through bugs ordered according to bug number
    • View bug information on one page. Click on the next or previous link will display the next or previous bug according to bug number
    • If the user is specfied as a developer or as the instructor of the course, then certain fields will be editable such as status and comments
  • Search
  • Reports
    • The reports page will display a list of predetermined queries that the instructor of the course or developers can create. A report will be customizable to display summaries only, the full report, or compiled in a format similar to release notes. There will also be a printer-friendly version of a report (and hopefully a downloadable version as .txt or .csv / .xls)
• Admin Page
  • The Admin Page will allow instructors of a course to administrate the bug tracker. The page will allow instructors to create new bug categories. The Admin page will also allow the instructors of a course to specify which users are developers (a new type of user). When users are specified as a developer for a bug tracker, they will then be able to edit a developer profile.
  • In an effort to make the bug tracker as generic and customizable as possible, administrating the bug tracker is similar to administrating a quiz. In a quiz, there are three parts: the quiz body, the quiz category, and the quiz questions. In the bug tracker, there are two parts: the bug tracker and the bug category.
    • The bug tracker is analogous to the quiz body in that both contain settings that are considered common to all bug trackers and quiz bodies respectively.
    • The bug category is analogous to the quiz QUESTION, in that there will be multiple types (drop-down menu, radio buttons, text fields, checkboxes) and each type will have their own settings. For example, a drop-down menu will have category items that will require user input to specify the items in the drop-down menu whereas the text field is simple and may not require any setup.
• Profile
  • The profile page will allow users specified as the developer of a bug tracker to be able to change certain preferences like email subscriptions and so forth.

Implementation

• Create database, tables, etc.
• Create bug database access library
  • Getter, setters, etc.
• Create bug submission form
• Submit to database
• Create View bug form
• Incorporate Moodle Authentication

Tentative Timeline / Milestones

June 28, 2006

• First Deliverable - Prototype

July 7, 2006 - July 14, 2006

• User Testing

July 14, 2006

• Start migrating old Moodle Bugs

July 28, 2006

• Second Deliverable - Prototype 2

July 28, 2006 - August 14, 2006

• QA & Fix bugs
• Accessibility Compliance?

August 7 - August 21, 2006

• Documentation

August 21, 2006

• Final Deliverable - Finished Product