Freshservice Project Management is built for IT initiatives: rollouts, migrations, audits, M&A integrations. The kind of work that has tasks, dependencies, and a delivery date but is not a single ticket. Used right, it replaces a separate Jira or Asana for IT-internal work.
When projects fit
Projects work when:
- Effort spans more than one team.
- There are dependencies between tasks.
- The work has a delivery date and stakeholders who want status.
- You need to associate the work with assets, changes, or requesters.
Skip projects for:
- Single-team work with no dependencies (use a parent ticket).
- Long-running operational work with no end date (use a service catalog item).
- Customer-facing delivery work (use a separate PSA tool; Freshservice projects are internal).
Project structure
A project has tasks, milestones, and dependencies. Tasks have assignees, due dates, and effort estimates. Milestones group tasks. Dependencies block successor tasks until predecessors complete.
Keep projects under 50 tasks. Above that, the Gantt view becomes unreadable and update overhead exceeds project value. Break large initiatives into multiple linked projects (phase 1, phase 2).
Task assignment
Tasks assign to agents, not to groups. This is a cleaner model than ticket round-robin because project tasks have known scope. Assign by skill, communicate, and let people manage their own workload.
For external (vendor) tasks, create a “Vendor” agent type or use the contact field to track external assignees outside the assignment dropdown.
Linking projects to tickets and changes
A project can link to multiple tickets and changes. Use this to associate “discovered work” (incidents, change requests) with the parent initiative. The project status report shows linked items and their status.
Link from the ticket side too: a custom field on the ticket “linked_project” lets you query all tickets touching a project. Useful for impact analysis when the project hits a delay.
Templates
Save common project structures as templates. The big three:
- Office relocation (network, desks, asset transfer, badging).
- New employee onboarding for a department of N (laptops, accounts, training, badge access).
- Application rollout (procurement, install, training, support handover).
Templates live under Project Management settings. Each template includes pre-built tasks, milestones, dependencies, and assignment rules.
Status reporting
Project status is roll-up: percent of tasks complete, overdue tasks, milestones missed. Stakeholders want a one-page status. Build a custom report that exports the status to PDF weekly and emails it to the project sponsor.
Manual status updates (“yellow because of blocked task X”) need a custom field on the project for narrative. The auto-rollup percent does not capture risk.
Resource capacity
Each agent has a capacity (set in their profile). Project tasks count against capacity. The project view warns when an agent is overcommitted. This is the only built-in workload signal in Freshservice.
In practice, capacity numbers are aspirational. Use the warning as a conversation starter, not a hard block.
Closing projects
Close a project when all tasks are complete or when the work is canceled. Closed projects are read-only and roll into project history. Do not delete projects; the audit trail of “we tried this” is valuable.
What to do this week
Pick one current cross-team initiative and try a project for it. Build the tasks, milestones, and dependencies in 30 minutes. Run it for two weeks and decide if you keep using it.
