Key Concepts of Project Management
Projects
Projects are the containers for all related work (Tickets). They organize tasks into logical groups and are defined by a unique, short identifier.
| Property | Description | Format/Example |
| What They Are | Containers for related tickets; organize work | Logical Groups |
| Key | Unique identifier | 2-10 uppercase characters (e.g., WEB, GAME) |
| Name | Full title | "Website Redesign," "New Game Development" |
| Lifecycle | Can be created, updated, and archived when complete. | - |
Tickets
Tickets are the individual tasks or work items that track specific work to be done. Every ticket belongs to exactly one project.
| Property | Description | Example |
| What They Are | Individual tasks; unit of work | - |
| Key | Unique identifier combining project key and number | WEB-45, GAME-123 |
| Core Properties | Summary, Description, Type, Status, Assignee, Reporter, Priority. | - |
| Lifecycle | Created $\to$ Assigned $\to$ Status Updated $\to$ Completed $\to$ Archived. | - |
Ticket Types
Ticket Types categorize the nature of the work, allowing for better organization and filtering. These types are customizable and can be assigned unique colors.
| Type | Purpose |
| Bug | Something broken that requires fixing. |
| Task | Regular, general work to be done. |
| Feature | New functionality to be added. |
| Improvement | Enhancement or update to existing functionality. |
| Custom | Types specific to your business needs (e.g., Maintenance, Question). |
Statuses
The Status defines the current state of a ticket and tracks its progress through a defined workflow. Statuses are grouped into three primary lifecycle stages.
| Stage | Typical Statuses | Description |
| Open | To Do | Work has been identified but not yet started. |
| In Progress | In Progress, In Review | Work is actively being done or is awaiting verification. |
| Done | Done | Work is completed and accepted. |
| Other | Blocked, On Hold | Used for temporary workflow interruptions. |
Priorities
Priorities determine the importance and urgency of a ticket, helping teams order and focus their work.
| Level | Description | Icon/Color | Use Case |
| Highest | Critical, must be addressed immediately. | Red (Double Up Arrow) | Urgent problems. |
| High | Important, should be done soon. | Red (Up Arrow) | Key project milestones. |
| Medium | Normal priority for standard tasks. | Orange (Dash) | Default tasks. |
| Low | Can wait until higher priority tasks are complete. | Blue (Down Arrow) | Small improvements. |
| Lowest | Nice-to-have, do only when time allows. | Blue (Double Down Arrow) | Backlog ideas. |
Time Tracking
Time tracking allows for planning (estimates) and measurement (logs) of effort spent on tickets.
- Time Estimates: The expected time to complete the work, set during ticket creation.
| Format: Weeks (w), Days (d), Hours (h), Minutes (m). |
| Example: 1w 2d 3h 30m |
- Time Logs: The actual time spent working. Logs track start/end times and allow comparison against the initial estimate.