makeplane / makeplane/plane

[feature]: Project-level time tracking analytics and worklogs

Open
#8,045 7 comments 2 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Oct 30, 2025.

✨feature
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary
Problem

While Plane tracks time at the work item level, there's no aggregated view of time data at the project level. This makes it impossible to get a holistic view of project health, budget utilization, or team time allocation without manual calculations.

Current behavior
  • Worklogs only visible within individual work items
  • No project-wide time properties
  • No way to see worklogs about a single project (without going through several steps)
  • Must export data or manually sum tracked time
  • No time tracking properties in the dashboard widgets
Expected behavior
  1. **Project Overview *

    • Display total tracked time for entire project
    • Display total estimated time (sum of all work item estimates)
    • Show utilization percentage (tracked/estimated)
    • Time breakdown by module/cycle/team member
  2. Project Worklogs View

    • New "Worklogs" tab at project level
    • Filterable by date range, team member, work item type
    • Exportable for invoicing/reporting
    • Bulk edit capabilities
Use case

As a project manager, I need to:

  1. Answer "How many hours have we spent on Project X?" without opening 100+ items
  2. Generate monthly time reports for client invoicing
  3. Identify which team members are logging time and on what
  4. Compare estimated vs actual time at project level to improve future estimates
Why should this be worked on?

This would transform Plane from a task tracker into a complete project management solution for agencies. Competitors are better at time reporting but lack Plane's project management features (to me, I like the simplicity of Plane) and this would give Plane the best of both worlds.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.