Ticket Properties¶

Ticket types, statuses, priorities and severities are managed by administrators in the AdminCP and are shared by all projects. Changing one changes it everywhere.

Property	AdminCP page
Types	`/admin/tickets/types`
Statuses	`/admin/tickets/statuses`
Priorities	`/admin/priorities`
Severities	`/admin/severities`

Milestones, versions and components are per project and are managed in Project Settings instead. For project-specific properties, see Custom Fields.

Ticket types¶

Types categorise tickets (what kind of work it is).

Option	Description
Name	Display name
Bullet	Used by the changelog to label tickets. `+`, `-` and `*` are the values it recognises
Changelog	Whether tickets of this type appear in the changelog
Template	Text pre-filled in the description when this type is chosen on the new ticket form

Defaults:

Type	Bullet
Defect	`-`
Feature Request	`+`
Enhancement	`*`
Task	`*`

Ticket templates¶

When a user picks a type on the new ticket form, the description editor is replaced with that type's template. Use it to ask for the information you need, for example steps to reproduce for a Defect:

## Steps to reproduce

1.

## Expected result

## Actual result

A template is plain text inserted into the description editor (rendered as Markdown when the Markdown plugin is enabled). Leave it empty for a blank description. Selecting another type replaces whatever is currently in the description with that type's template.

Statuses¶

Statuses describe where a ticket is in its life cycle.

Option	Description
Name	Display name
Status	The status type: Open, Started or Closed
Changelog	Whether tickets with this status appear in the changelog

The type is what Traq uses, not the name:

A ticket is closed when its status has the Closed type. Moving a ticket to or from a closed status is what closes or reopens it.
Open and Started tickets both count as open. Started marks work in progress.
Ticket list filters use these groups: ?status=allopen, ?status=allstarted and ?status=allclosed.

Defaults:

Status	Type	In changelog
New	Open	No
Accepted	Open	No
Started	Started	No
Closed	Closed	Yes
Completed	Closed	Yes

Closing, reopening and updating tickets sends notifications to subscribers.

Priorities¶

Priorities say how soon a ticket should be dealt with. Only a name is stored. Defaults, from highest to lowest: Highest, High, Normal, Low, Lowest.

When a ticket list is sorted by priority or severity, it is ordered by the property's ID, not alphabetically. Create new ones in the order you want them ranked.

Severities¶

Severities say how serious a problem is. Only a name is stored. Defaults: Blocker, Critical, Major, Normal, Minor, Trivial. New tickets default to Normal severity and Normal priority.

The changelog¶

A project's changelog (/{project}/changelog, also available as an Atom feed) lists the tickets of every completed milestone. A ticket is included only if both its type and its status have Changelog enabled. With the defaults, that means closed or completed Defects, Feature Requests, Enhancements and Tasks.

Tickets are labelled by their type's bullet:

Bullet	Label
`+`	New
`-`	Fix
`*`	Enhancement

Using properties in the ticket list¶

Filter and sort by these by name:

/{project}/tickets?type=Defect&status=allopen
/{project}/tickets?priority=Highest,High&severity=!Trivial
/{project}/tickets?order_by=priority.asc

Names are matched exactly (milestones and versions by slug). Separate several values with commas and prefix with ! to exclude. The full list of filters is in the API reference.

API¶

The lists are available as JSON:

GET /api/types, /api/statuses, /api/priorities
Admins can also list and manage them through the admin endpoints.