Task
Overview
Task — Business Overview
Task is a core planning and execution record in Dafater used to define, assign, track, and control individual pieces of work within a project or ongoing operation. It helps organizations turn high-level plans into clear, actionable activities with ownership, timelines, and accountability.
What Task Is Used for in Business Operations
A Task represents a specific unit of work that needs to be completed by a person or team. It is used to:
- Break projects into manageable actions
- Assign responsibility and due dates
- Track progress and completion status
- Coordinate work across teams and departments
- Ensure accountability and timely delivery
By using Tasks, businesses gain visibility into who is doing what, by when, and at what stage.
Prerequisites and Setup Requirements
Before using Task effectively, the following should be in place:
- Projects or work initiatives defined, so Tasks can be linked to meaningful business goals
- Employees or users identified, to allow proper assignment and ownership
- Clear business objectives and timelines, so Tasks are aligned with priorities
- Standard task statuses agreed upon (such as Open, In Progress, Completed) for consistent tracking
This preparation ensures Tasks are not created in isolation but contribute to structured execution.
Typical Workflow and Business Process Fit
Task Creation
A Task is created when a piece of work is identified—either during project planning or as work arises during operations.Assignment and Scheduling
The Task is assigned to a responsible person, with expected start and end dates.Execution and Monitoring
The assigned person works on the Task while managers monitor progress and workload.Updates and Collaboration
Status updates, notes, or changes help keep everyone informed and aligned.Completion and Review
Once finished, the Task is marked complete and contributes to overall project or operational success.
This workflow ensures structured execution and minimizes missed responsibilities.
Key Business Scenarios Where Task Is Essential
Project Delivery
Managing design, development, implementation, or rollout activities.Operational Work Management
Tracking recurring or ad-hoc work such as audits, maintenance, or internal initiatives.Cross-Department Coordination
Aligning work across teams where dependencies and timelines matter.Employee Accountability
Clearly defining responsibilities and measuring completion.Deadline-Driven Work
Ensuring critical actions are completed on time to meet client or business commitments.
Important Considerations for Users
- Be specific and clear when defining a Task to avoid confusion or rework
- Assign realistic deadlines based on effort and availability
- Keep Task statuses up to date to maintain accurate visibility
- Avoid creating Tasks without ownership, as unassigned work often gets delayed
- Review Tasks regularly to identify bottlenecks or overloads early
When used consistently, Task becomes a powerful tool for discipline, transparency, and execution excellence in Dafater.
In summary, Task is essential for translating plans into action, ensuring accountability, and delivering results efficiently across projects and daily business operations.
Basic Information
- Module: Projects
- Document Type: Setup
Fields
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| subject | Subject | Data | ✓ | - | Short title summarizing the task objective or deliverable |
| project | Project | Link | Project | Associated project under which this task is planned and tracked | |
| issue | Issue | Link | Issue | Related issue or ticket linked to this task | |
| type | Type | Link | Task Type | Business classification defining the task category | |
| color | Color | Color | - | Visual color indicator for task identification | |
| is_group | Is Group | Check | - | Indicates whether this task groups multiple subtasks | |
| is_template | Is Template | Check | - | Marks task as reusable template for future tasks | |
| status | Status | Select | Open, Working, Pending Review, Overdue, Templat... | Current business status of the task | |
| priority | Priority | Select | Low, Medium, High, Urgent | Urgency level determining task execution order | |
| task_weight | Weight | Float | - | Relative weight for task contribution or progress calculation | |
| parent_task | Parent Task | Link | Task | Parent task for hierarchical task structuring | |
| completed_by | Completed By | Link | User | User who marked the task as completed | |
| completed_on | Completed On | Date | - | Date when the task was completed | |
| expstartdate | Expected Start Date | Date | - | Planned start date for task execution | |
| expected_time | Expected Time (in hours) | Float | - | Estimated effort required to complete the task | |
| start | Begin On (Days) | Int | - | Number of days after project start to begin task | |
| expenddate | Expected End Date | Date | - | Planned completion date for the task | |
| progress | % Progress | Percent | - | Percentage of task completion achieved | |
| duration | Duration (Days) | Int | - | Planned task duration in days | |
| is_milestone | Is Milestone | Check | - | Indicates task represents a key project milestone | |
| description | Task Description | Text Editor | - | Detailed business description of task requirements | |
| depends_on | Dependent Tasks | Table | Task Depends On | List of tasks that must be completed first | |
| dependsontasks | Depends on Tasks | Code | - | System-generated task dependency details | |
| actstartdate | Actual Start Date (via Timesheet) | Date | - | Actual task start date from timesheets | |
| actual_time | Actual Time in Hours (via Timesheet) | Float | - | Total actual hours logged via timesheets | |
| actenddate | Actual End Date (via Timesheet) | Date | - | Actual task completion date from timesheets | |
| totalcostingamount | Total Costing Amount (via Timesheet) | Currency | Company:company:default_currency | Total internal cost incurred for this task | |
| totalexpenseclaim | Total Expense Claim (via Expense Claim) | Currency | Company:company:default_currency | Total employee expenses claimed against this task | |
| totalbillingamount | Total Billable Amount (via Timesheet) | Currency | - | Total billable amount generated from this task | |
| review_date | Review Date | Date | - | Scheduled date for task review | |
| closing_date | Closing Date | Date | - | Date when task was formally closed | |
| department | Department | Link | Department | Department responsible for executing the task | |
| company | Company | Link | Company | Company under which this task is managed | |
| lft | lft | Int | - | System field for hierarchical task ordering | |
| rgt | rgt | Int | - | System field for hierarchical task ordering | |
| old_parent | Old Parent | Data | - | Previous parent task before restructuring | |
| template_task | Template Task | Data | - | Reference to originating task template |
Child Tables
Dependent Tasks (Task Depends On)
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| task | Task | Link | Task | Dependent task in Dafater required before this task starts | |
| subject | Subject | Text | - | Summary of dependent task subject in Dafater | |
| project | Project | Text | - | Associated project for the dependent task in Dafater |
Permissions
| Role | Read | Write | Create | Delete | Submit | Cancel |
|---|---|---|---|---|---|---|
| Projects User | ✓ | ✓ | ✓ | ✓ |
Related DocTypes
| DocType | Relationship | Module |
|---|---|---|
| Expense Claim | Linked from | HR |
| Company | Links to | Setup |
| Department | Links to | Setup |
| Issue | Links to | Support |
| Project | Links to | Projects |
| Task | Links to | Projects |
| Task Type | Links to | Projects |
| User | Links to | Core |