|This page has links to websites or programs not trusted by Scratch or hosted by Wikipedia. Remember to stay safe while using the internet, as we can't guarantee the safety of other websites.|
|This article or section documents something not included in the current version of Scratch (3.0). It is only useful from a historical perspective.|
The bugtracker was a tool used for recording bugs that needed to be fixed and new features that users wanted in Scratch. It allowed developers to see a list of bugs and features that need to be fixed or made. It was different from the Bugs and Glitches forum because only responsible individuals approved by the Scratch Team could add issues, and the bugtracker also had features that allowed for better tracking of issues. The bug tracker is now obsolete, as the Scratch Team uses GitHub now.
Every issue was put in one of five projects. Each issue would go in different places depending on what area of Scratch it concerned. The projects were:
- Scratch 2.0 Cloud Data
- Forums 2.0
- Paint Editor
- Project Editor
- 2.0 Website
Each issue on the bugtracker had a title, a status, a priority level, an assignee, a category, a target version, a description, and indication of either a bug or a feature.
The title of the issue appeared on the main page where all the issues were listed and on the issue's page.
A status indicated how far the developers have got to completing the fix or feature. Most statuses were either "New," "Pre-Flight," "Feedback" or "Closed."
- Priority Level
Some issues were more important than others, so they all had different titles to determine their importance. Levels: Low, Normal, High, Urgent, and Immediate.
Different issues were assigned to be fixed or made by different people. The "assignee" category allows different people to be assigned different tasks.
A category was used to categorize an issue. The category was only viewable on the issue's page.
- Target version
Each issue on the bugtracker had a target version. The target version was the version of Scratch the feature should be included in.
The description, which was only shown on an issue's page, was the place where bugtracker users could provide more detail.
For Scratch 1.x, there was a different bugtracker. It was similar and each ticket had a milestone, an assignee, a status, a title, and a description. The first ticket was created in 2008 by andresmh and the last in 2013 by Paddle2See. There were 546 tickets created in total.