Task Property 

Description 

Task Header 

View Task Tab 

Full Path 

Shows the full task path in the tasks hierarchy. 

Yes 

No 

Name 

Store Task Name, the size is limited to 160 bytes 

Yes 

Yes 

Category 

Tasks should have one of the following categories for easy management:
project - when you create a new project, select this category for the new task. A project can include other bugs or projects.
bug - bug/error/defect. When a project member finds a bug in the project, he/she should create a new task and assign it the bug category.
task - a project can include some subtasks. If you want to create a subtask, create a new task in the current project and select this category for it.
research - use this task category to add a research to your project.
question - a user can add task with this category, if he/she has any questions.
branch, release, module - these categories can be used for easy management of multiple related bugs.
You can extend category list for your project, if you wish. 

Yes 

Yes 

# 

Unique numeric task number. 

Yes 

Yes 

Deadline 

This is the date when the current task must be finished. 

Yes 

Yes 

Submit Date 

Date when the task was submitted. 

Yes 

Yes 

Last Updated 

Date of the last task update. The last update date for a project is the maximum of the last update of any of its subtasks. 

Yes 

Yes 

Close Date 

Date when the task was closed (if the task is closed) 

Yes 

Yes 

Priority 

Task priority. It can vary from low (lowest priority) to support (highest priority). The priority can be customized on a per-workflow basis. 

Yes 

Yes 

Budget 

Estimated time (in hours) allocated for the task. This is working time, not calendar time. 

Yes 

Yes 

Submitter 

The user who has submitted this task. 

Yes 

Yes 

Handler 

The current task handler. When the handler makes some changes to the task (for example, a developer fixes a bug), he/she can assign this task to another user (for example, to tester for checking) or leave it with the same handler. In either case, any task at any time can have only one handler responsible for it. This system helps avoid the situation when there are a lot of issues and nobody knows how to resolve them. 

Yes 

Yes 

Task Alias 

Alternative short task name, used in some places if available. Generally, you should set Task Alias for your projects. Alias names are also useful for jumping to tasks from the site title page. 

Yes 

Yes 

Actual budget 

Elapsed task processing time (working time, not calendar time). The actual budget for the project is the sum of actual budgets of current task and all its subtasks. 

Yes 

Yes 

Status 

Task state. Tasks with different status are highlighted with different colors. A newly created task has the new status. If a manager processes the task, its status changes to processing. After solving the task it becomes resolved. The task may be then verified (by a tester), and its status changes to verified. After the task is done it becomes closed. A task can be reopened, when its status is resolved, verified or closed. A reopened task gets the processing status. 

Yes 

Yes 

Resolution 

Resolution reflects the current task condition. It can be open, duplicate, fixed, not a bug, not fixable, suspended. 

Yes 

Yes 

Parent task 

A user can move the current task (with all subtasks) to another parent task.
The new parent of the task must meet the following requirements:
1) You have rights to view this task and add subtasks to it
2) This task is not a child of the moved task. 

No 

Yes 

Description 

Here you can place the task description, if its name is not informative enough. 

Yes 

Yes 

Custom Fields 

User-defined custom fields. 

Only marked as visible 

Yes