wiki:Developer/TicketTriage
Last modified 2 years ago

Ticket Triage

This page will attempt to provide guidelines when working with tickets.

Summary

  • 111 untriaged tickets (list)
  • 0 requesting feedback (list)
  • 114 Tickets that have been accepted for work. (list)

General Guidelines

Try to always add a comment when updating a ticket. If it's a simple state change that explains itself by the change then a comment isn't necessary.

Milestone

Milestones are used to track what tickets must be completed for a future release.

When to set a milestone

  • When setting a ticket into the 'fixed' state.
  • Schedule a ticket to be completed in a future release.

When NOT to set a milestone

For the situations below the milestone should be left blank.

  • If you don't know what version the ticket should be completed in.
  • If the resolution is either wontfix, invalid or worksforme.

Version

<number>
Set this to the version of Aegisub the ticket is referring to.
devel
If the ticket is based off of the CVS version then use this as the version.

Resolution

fixed
Use when the ticket has been resolved, for task tickets use when the task has been completed.
invalid
Ticket was incorrectly submitted or not usable.
wontfix
Not a feature we want to add, or an item that we believe is a bug.
duplicate
Duplicate of another ticket in the database. If using this put the referred ticket number in the comment when closing.
worksforme
Not a bug or feature already exists.
timeout
Set when a ticket is too old to be useful or a user hasn't responded with requested information.
  • Note: This is automatically set by 'timeout' when a ticket is in the infoneeded* state.

Ticket Types

defect
A bug or deficiency in Aegisub.
enhancement
A feature request or enhancement.
task
Not a bug or enhancement but a task item or TODO.

Component

Right now there are 6 general components:

  • Audio - Anything to with audio.
  • Docs - User documentation, either in-software or on the website.
  • General - No category.
  • Interface - Involves anything to do with the UI.
  • Scripting - Automation.
  • Video - Anything to do with Video.

Sub Component

The sub components speak for themselves, if one exists for a Component then it should be set. See below for more details on using Keywords to narrow the scope.

Platform

If the ticket is specific to a single platform then it should be set, if it involves 2 or more platforms then leave it as 'ALL'. Keywords can be used to narrow down the scope.

Keywords

When a ticket needs to be more specific, feel free to add as many keywords as you feel necessary, space delimited.

Feel free to add new categories or keywords, the purpose of this list is to ensure that we're uniform in what we use. It's also possible to add keywords that aren't common. In those cases don't add them to this list.

  • Platform
    • x86, x86_64
  • Scripting
    • input, output
  • Types
    • crash, race, frozen
  • Docs
    • website, manual, trac, wiki
  • Interface
    • wxgtk, wxmac, wxwindows, wxwidgets, timer, karaoke, editbox
  • Video
    • opengl, x11, aqua