makeplane / makeplane/plane

[feature]: Show tracked time property in work items overview/filter

Open
#8,043 0 comments 0 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

The 'tracked time' property is only visible inside individual work items, not in table/list/kanban views. For agencies and developers doing client work, this creates unnecessary friction when reviewing time logs across projects.

Current behavior
  • Tracked time only visible when opening individual work items
  • No way to filter/sort by tracked time
  • Must manually check each item for time entries
Expected behavior
  • Add 'Tracked Time' as a column option in all views (table/list/kanban)
  • Enable filtering: has tracked-time, tracked-time:>2h, etc.
  • Allow sorting by tracked time
Use case

As a developer billing clients hourly, I need to quickly:

  1. See which tasks have missing time entries before invoicing
  2. Identify tasks exceeding estimates
  3. Review total time per feature/module

Currently this requires opening 50+ items individually. With tracked time visible in views, this becomes a 10-second task.

Additional context

This would differentiate Plane from competitors like Linear/Jira where time tracking is often an afterthought. For agencies managing client projects, time visibility is as important as issue status.

Why should this be worked on?

As an initiative of making Plane easier to use for managing customer projects, one thing Plane can do to differentiate from competitors is removing friction from logging work and keeping time. This FR is related to this.

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.