Tasks & Milestones

Control & Direction

Tasks, milestones, and requirements are the building blocks of project execution. Tasks represent individual work items assigned to team members, milestones mark significant checkpoints in the project timeline, and requirements capture conditions that must be met before work can proceed. Together they provide the granular tracking needed to manage delivery within each project.

Tasks & Milestones are managed within Projects. Tasks can be linked to Team Goals and Individual Goals for goal traceability. Requirements support approval workflows tied to Project Lifecycle governance.

Task management

Tasks are managed from the project detail page. SecureHive supports both table view and Kanban board layouts for task management, allowing you to switch between a structured list and a visual drag-and-drop board.

Creating a task

Open the task form

From the project detail page, click Add Task. The task creation form opens with all available fields.

Provide task details

Fill in the following fields:

Field	Description	Required
Task Name	A concise description of the work item	Yes
Description	Detailed information about what needs to be done	No
Status	The initial status (defaults to To Do)	No
Assigned To	The team member responsible for completing the task	No
Start Date	When work on the task should begin	No
Due Date	The deadline for task completion	No
Priority	The task’s priority level	No
Estimated Hours	The expected effort in hours	No
Task Type	Either Task (standard work item) or Test (verification item)	No
Section	The section this task belongs to for organizational grouping	No
Tags	Labels for categorization and filtering	No

Link to goals (optional)

Select a Team Goal or Individual Goal to connect the task to a specific objective. This creates traceability from the task level up to team and CISO-level goals.

Link to a requirement (optional)

Select a Requirement to associate the task with a project requirement. This connects execution work to the requirements that authorize it.

Save

Click Save to create the task. It will appear in the project’s task list and on the Kanban board under the appropriate status column.

Task statuses

Tasks move through the following statuses as work progresses:

Status	Description
To Do	The task has been defined but work has not started
In Progress	Active work is underway on the task
Blocked	Work cannot continue due to a dependency, missing information, or external constraint
Completed	The task has been finished and all acceptance criteria have been met

Update the status from the task list, the Kanban board (drag and drop), or the task detail view.

Task types

Each task has a task type that determines its purpose within the project:

Type	Purpose
Task	A standard work item representing a deliverable or action to be completed
Test	A verification item used to confirm that a requirement or deliverable meets acceptance criteria

Test confirmation

Tasks with the Test type include an additional Test Confirmation Status field that tracks the outcome of the test:

Confirmation Status	Meaning
Pending	The test has not yet been executed or the result has not been recorded
Confirmed	The test has passed and the associated requirement or deliverable is verified
Failed	The test did not pass and further work is needed before the requirement can be considered met

Test confirmation provides a lightweight verification mechanism that integrates with the requirements and lifecycle approval process.

Sections

Sections allow you to organize tasks into logical groups within a project. Each section has a name and an order, and tasks are assigned to a section during creation or editing. Use sections to separate tasks by workstream, phase, or functional area. Sections appear as grouping headers in the table view and as swimlanes or column groups depending on the layout.

Subtask hierarchy

Tasks support a parent-child hierarchy through the parent task reference. Create subtasks by selecting a parent task when creating a new task. This allows you to break down complex work items into smaller, trackable pieces while maintaining the relationship to the parent deliverable. Subtasks inherit the project context but have their own status, assignee, and due date.

Dependencies

Tasks can declare dependencies on other tasks within the same project. Dependencies are stored as a list of task references and indicate that a task should not start until its dependencies are complete. Use dependencies to model sequencing constraints and identify potential bottlenecks in your project plan.

Time tracking

Each task tracks Estimated Hours and Actual Hours to provide visibility into effort allocation. Enter estimated hours during task creation and update actual hours as work is performed. The difference between estimated and actual hours helps project managers identify tasks that are taking longer than expected and adjust plans accordingly.

Milestones

Milestones represent significant checkpoints or deliverables in the project timeline. Unlike tasks, milestones do not represent work to be done but rather a point in time when a key outcome should be achieved.

Creating a milestone

From the project detail page, click Add Milestone and provide the following fields:

Field	Description	Required
Milestone Name	A descriptive title for the checkpoint	Yes
Description	Context about what this milestone represents	No
Target Date	The date by which the milestone should be achieved	No
Success Criteria	A list of conditions that define when the milestone is met	No
Related Tasks	References to tasks that contribute to achieving this milestone	No

Milestone statuses

Milestones move through the following statuses:

Status	Description
Pending	The milestone has been defined but the target date has not been reached
In Progress	Work toward the milestone is actively underway
Achieved	All success criteria have been met and the milestone is complete
Delayed	The milestone has missed its target date and has not yet been achieved

When a milestone is achieved, the Achieved Date is recorded automatically.

Requirements

Requirements capture the conditions, specifications, or criteria that must be satisfied within a project. They provide a formal layer of governance between what needs to be done and the tasks that deliver it.

Creating a requirement

From the project detail page, navigate to the requirements section and click Add Requirement. Provide the following fields:

Field	Description	Required
Title	A concise statement of the requirement	Yes
Description	Detailed explanation of the requirement and acceptance criteria	No
Order	The display order within the project’s requirement list	No

Requirements are created in Draft status.

Requirement status lifecycle

Requirements follow a defined approval flow:

Status	Description
Draft	The requirement is being authored and is not yet ready for review
Pending Approval	The requirement has been submitted for review by an approver
Approved	The requirement has been reviewed and accepted. The approver, approval date, and a snapshot of the approved content are recorded.
Rejected	The requirement was not accepted. A rejection reason is captured for the author to address.
Converted	The requirement has been converted into one or more tasks for execution

When a requirement is approved, the system records the Approved By user, the Approved At timestamp, and an Approval Snapshot preserving the requirement as it existed at the time of approval. If a requirement was delegated, the Delegated From User reference tracks who originally submitted it.

Linking requirements to tasks

Approved or converted requirements can be linked to tasks. Each task has an optional Requirement reference, creating a direct connection between the authorization (requirement) and the execution (task). Tasks with the Test type are particularly useful for verifying that a requirement has been satisfied.

Attachments

Tasks support file attachments for associating relevant documents, screenshots, or other files with specific work items. Attachments are stored as references on the task and are accessible from the task detail view.

Permissions

Managing tasks, milestones, and requirements requires the projects:manage permission. Users with this permission can create, edit, and delete tasks, milestones, and requirements within projects they have access to. Requirement approval actions are governed by the project’s lifecycle configuration and approver settings. Users with projects:read can view tasks and milestones but cannot make changes.