tbl_task

-1 rows


Description

Module: Task Management
Purpose: Stores daily task information assigned to employees.
Data: One row per task, containing task metadata, assignment info, attachments, and timing details.
Process Usage:
- Used to track tasks assigned to employees, including recurring and non-recurring tasks.
- Supports linking to projects, templates, and sub-tasks.
- Stores attachments in JSON format for screenshots or other files.
Key Points:
- Tracks total time spent on the task and extended deadlines.
- Supports hierarchical tasks with recurring parent references.
- Linked to tbl_task_hours for individual employee effort tracking.
Business Impact: Enables task management, progress tracking, and reporting for projects and daily operations.

Columns

Column Type Size Nulls Auto Default Children Parents Comments
id bigserial 19 √ nextval('tbl_task_id_seq'::regclass)

Primary key
Format: BIGSERIAL (auto-increment)
Used as: Unique identifier for each task.
taskname varchar 150 null

Task Name
Format: VARCHAR(150)
Meaning: Name or title of the daily task.
Usage: Displayed in dashboards, task lists, and reports.
employeeid varchar 500 null
tbl_employee.employeeid Implied Constraint R

Employee ID
Format: VARCHAR(500)
Meaning: ID of the employee to whom the task is assigned.
Usage: Links the task to the assigned employee.
projectid int8 19 √ null

Project ID
Format: BIGINT
FK: tbl_project.id
Meaning: The project this task belongs to.
Usage: Associates tasks with projects for reporting and progress tracking.
tasktype varchar 100 null

Task Type
Format: VARCHAR(100)
Possible Values: RECURRING, NON_RECURRING
Usage: Determines how task recurrence is handled.
recurringparentid int8 19 √ null

Recurring Parent ID
Format: BIGINT
FK: tbl_recurringTask.id
Meaning: References the parent task if this is part of a recurring series.
Usage: Tracks parent-child relationship for recurring tasks.
templateid int8 19 √ null

Template ID
Format: BIGINT
FK: tbl_project_template.id
Meaning: Template used to create this task.
Usage: Helps standardize task creation.
startdate date 13 √ null

Start Date
Format: DATE
Meaning: When the task is scheduled to start.
Usage: Used for scheduling, reminders, and reporting.
enddate date 13 √ null

End Date
Format: DATE
Meaning: Task completion target date.
Usage: Used for monitoring deadlines and overdue tasks.
totalspenttime int8 19 √ null

Total Time Spent
Format: BIGINT
Meaning: Total minutes spent on the task by all employees.
Usage: Aggregated from tbl_task_hours.
extendedenddate date 13 √ null

Extended End Date
Format: DATE
Meaning: If the task deadline was extended, stores the new end date.
Usage: Monitors changes to task timelines.
attachment text 2147483647 √ null

Attachments
Format: TEXT (JSON)
Meaning: Uploaded files related to the task.
Usage: JSON array storing file name, system path, upload date, and uploader.
taskdescription varchar 1000 √ null

Task Description
Format: VARCHAR(1000)
Meaning: Detailed description of the task.
Usage: Helps employee understand the task requirements.
createddate timestamp 29,6 √ null
createdby varchar 500 √ null
modifieddate timestamp 29,6 √ null
modifiedby varchar 500 √ null
projectsubtaskid varchar 500 √ null

Project Subtask ID
Format: VARCHAR(500)
Meaning: Stores task numbers of subtasks if this task belongs to a larger project task.
Usage: Supports hierarchical project task tracking.
review_id int8 19 √ null
tbl_task_hours.id fk_review_id N

Task Hours Review ID
Format: BIGINT
FK: tbl_task_hours.id
Meaning: References employee effort record.
Usage: Links task to detailed time tracking.

Indexes

Constraint Name Type Sort Column(s)
pk__tbl_task_id Primary key Asc id

Relationships

Close relationships within degrees of separation