Skip to content

Added missing features#395

Merged
sriramveeraghanta merged 1 commit intomasterfrom
new-features-29-01-26
Feb 2, 2026
Merged

Added missing features#395
sriramveeraghanta merged 1 commit intomasterfrom
new-features-29-01-26

Conversation

@danciaclara
Copy link
Copy Markdown
Collaborator

@danciaclara danciaclara commented Feb 2, 2026

Description

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Improvement (change that would cause existing functionality to not work as expected)
  • Code refactoring
  • Performance improvements
  • Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

  • Documentation
    • Fixed broken links and improved markdown formatting
    • Expanded filter operator reference with new field documentation and "is empty" operators
    • Added Timeline layout documentation for milestone visualization
    • Updated minimum mobile version requirement from v1.5.0 to v1.12.0
    • Improved documentation structure and organization

@vercel
Copy link
Copy Markdown

vercel Bot commented Feb 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Feb 2, 2026 2:35pm
docs-vitepress Error Error Feb 2, 2026 2:35pm

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 2, 2026

📝 Walkthrough

Walkthrough

These changes consist of documentation updates across multiple files, including a Markdown link correction in the AI chat guide, heading level adjustments in cycles documentation, expanded operator reference sections with "is empty" entries in filter documentation, a new Timeline layout subsection for milestones, and a version requirement update for mobile devices.

Changes

Cohort / File(s) Summary
Link and Structure Corrections
docs/ai/pi-chat.mdx, docs/core-concepts/cycles.mdx
Fixed Markdown link by moving descriptive text outside the anchor in pi-chat; promoted "Benefits" and "Configuration" heading levels from three to four in cycles.
Operator and Feature Documentation Expansion
docs/core-concepts/issues/visualise_filter.mdx, docs/core-concepts/projects/milestones.mdx
Added comprehensive operator reference sections with "is empty" entries across multiple fields in visualise_filter; introduced new "View milestones in Timeline layout" subsection with visual descriptions in milestones.
Version Requirements Update
docs/devices/mobile.mdx
Updated minimum version reference from v1.5.0 to v1.12.0 for Cloud and self-hosted sign-in requirements.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hops through docs with eager cheer,
Links are fixed, the path is clear!
Headings aligned, operators shine,
Timeline views and versions fine—
Documentation, neat and bright,
Everything's just right!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Added missing features' is vague and generic, failing to convey what features were actually added or modified across the multiple documentation files changed. Revise the title to be more specific about the main changes, such as 'Update documentation with operator references and mobile version requirements' or similar, to clearly communicate the primary intent of the changeset.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch new-features-29-01-26

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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@docs/core-concepts/issues/visualise_filter.mdx`:
- Line 211: The header "### Start date, Due date, Created at, and Updated at"
uses "Due date" while examples use "Target date"; pick one term and make them
consistent across the document by updating the header or the example
occurrences. Search for the phrase "Target date" (seen in examples) and the
header string and replace all instances so the header and examples use the same
terminology (either change the header to "Target date" or update the example
text to "Due date") ensuring matching capitalization and pluralization in
functions/sections that reference them.

In `@docs/devices/mobile.mdx`:
- Line 30: The Troubleshooting section still references the older minimum
version string "Ensure your Plane instance is running the Commercial Edition
version `v1.5.0` or higher."; update that string to use `v1.12.0` so it matches
the new minimum stated earlier and avoid version inconsistency in the
Troubleshooting section.
🧹 Nitpick comments (1)
docs/core-concepts/cycles.mdx (1)

106-112: Consider using h3 (###) instead of h4 (####) for consistent heading hierarchy.

These subsections skip from h2 (Auto-schedule cycles) directly to h4, bypassing h3. This creates an inconsistent document outline and may affect accessibility for screen readers and SEO. Other similar subsections in this document (e.g., "Cycle summary", "Burn-down chart") use h3 (###).

📝 Suggested fix
-#### Benefits
+### Benefits
 - Maintain regular cycle rhythms automatically without manual intervention.
 ...

-#### Configuration
+### Configuration

| `is empty` | No module assigned | Items not in any module |

### Start date and Target date
### Start date, Due date, Created at, and Updated at
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Terminology inconsistency: "Due date" vs "Target date".

The header uses "Due date" but the examples throughout the document (lines 39, 50, 58, 229) consistently use "Target date". Consider using consistent terminology:

-### Start date, Due date, Created at, and Updated at
+### Start date, Target date, Created at, and Updated at

Alternatively, update the examples to use "Due date" if that's the preferred terminology going forward.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Start date, Due date, Created at, and Updated at
### Start date, Target date, Created at, and Updated at
🤖 Prompt for AI Agents
In `@docs/core-concepts/issues/visualise_filter.mdx` at line 211, The header "###
Start date, Due date, Created at, and Updated at" uses "Due date" while examples
use "Target date"; pick one term and make them consistent across the document by
updating the header or the example occurrences. Search for the phrase "Target
date" (seen in examples) and the header string and replace all instances so the
header and examples use the same terminology (either change the header to
"Target date" or update the example text to "Due date") ensuring matching
capitalization and pluralization in functions/sections that reference them.

Comment thread docs/devices/mobile.mdx
## Sign in

The app is available on Cloud and for self-hosted instances on all plans of the Commercial Edition starting from version `v1.5.0`. Here’s how you can get started:
The app is available on Cloud and for self-hosted instances on all plans of the Commercial Edition starting from version `v1.12.0`. Here’s how you can get started:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Version inconsistency with Troubleshooting section.

Line 30 updates the minimum version to v1.12.0, but the Troubleshooting section at line 194 still references v1.5.0:

Ensure your Plane instance is running the Commercial Edition version v1.5.0 or higher.

This inconsistency may confuse self-hosted users. Consider updating line 194 to also reference v1.12.0 for consistency.

🤖 Prompt for AI Agents
In `@docs/devices/mobile.mdx` at line 30, The Troubleshooting section still
references the older minimum version string "Ensure your Plane instance is
running the Commercial Edition version `v1.5.0` or higher."; update that string
to use `v1.12.0` so it matches the new minimum stated earlier and avoid version
inconsistency in the Troubleshooting section.

@sriramveeraghanta sriramveeraghanta merged commit 337c272 into master Feb 2, 2026
3 of 4 checks passed
@sriramveeraghanta sriramveeraghanta deleted the new-features-29-01-26 branch February 2, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants