Fixes #8043 — Add tracked time column and filtering to work items view

[tapchan54]

• Added 'Tracked Time' column to work items table
• Added filter to show only items with tracked time
• Added sorting by tracked time
• Uses mock data for now

Summary by CodeRabbit

• Chores
  • Updated project dependencies.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

Updates a submodule pointer to reference a new commit in the subproject. This is a single-line change that advances the submodule to a different commit state, with no modifications to code, logic, or public APIs.

Changes

Cohort / File(s)	Summary
Submodule pointer update plane	Subproject commit reference updated to a new commit SHA

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• This is a routine submodule pointer update requiring minimal scrutiny, assuming the target commit is verified and intentional.

Poem

🐰 A tiny hop forward,
One commit at a time,
The plane submodule soars,
On the path to what's fine!
✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is largely incomplete and does not follow the required template structure. The description is provided only as bullet points and lacks all required sections including the main Description section header, Type of Change checkboxes, Screenshots/Media section, Test Scenarios, and References section. While the bullet points contain some relevant information about the changes, the description fails to adhere to the specified template format that would help maintainers understand the nature of the change and verification approach.	The author should update the PR description to match the required template, including sections for Type of Change (selecting appropriate checkboxes), Screenshots/Media demonstrating the new functionality, Test Scenarios describing verification steps, and References linking to the related issue (#8043). A comprehensive description following the template structure will improve clarity for reviewers and maintainers.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	There is a critical conflict between the provided information sources. The raw_summary explicitly states "Adds a single-line Subproject commit entry indicating a submodule update. No code, logic, or public API changes are introduced," while the PR objectives describe substantial feature additions including a tracked time column, filtering, and sorting functionality. The title directly aligns with the PR objectives but appears unrelated to the raw_summary. This creates an inconclusive situation where the information provided is contradictory, making it impossible to definitively assess whether the title accurately reflects the actual changeset.	To resolve this, clarify the actual scope of changes in the PR. If the PR genuinely contains only a submodule update, the title needs to be updated to reflect that. If the PR contains the feature additions described in the objectives, the raw_summary should be verified for accuracy. Ensure consistency between the title, actual changes, and stated objectives before proceeding.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 961cdf6 and 7c24bff.

📒 Files selected for processing (1)

• plane (1 hunks)

🔇 Additional comments (1)

plane (1)

1-1: Verify the submodule update is intentional and necessary for this PR.

The submodule pointer has been updated to commit 961cdf6c8faab890339909b955275ea89b255e16, which fixes storybook build errors related to import path resolution. However, the stated PR objectives focus on adding tracked time columns and filtering—a feature that appears disconnected from these infrastructure fixes.

Could you clarify:

1. Is this submodule update a prerequisite/dependency for the tracked time feature work?
2. Are the actual feature implementation files (column definitions, filters, sorting logic) located elsewhere in the changeset (not shown in this review)?
3. Does the commit being referenced introduce any breaking changes to the plane submodule's public API?

If the actual tracked time feature files exist in this PR, please ensure they are included in the review scope for a complete assessment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}