Added CSV importer and other updates#420
Merged
sriramveeraghanta merged 5 commits intomasterfrom Mar 27, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 22 minutes and 22 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded a Flatfile importer page, sidebar entry, and SVG icon; relabeled two sidebar items; reworked CSV importer docs and importer overview; removed some availability callouts; and made several small copy/formatting updates across documentation pages. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (4)
docs/.vitepress/config.ts (1)
305-305: Align sidebar label with target page title for consistency.Line 305 uses “IdP Group Sync”, while the destination page title is “Manage project access with IdP groups” (
docs/authentication/group-sync.md, Line 2). Harmonizing phrasing will make navigation feel less fragmented.Possible adjustment
- { text: "IdP Group Sync", link: "/authentication/group-sync" }, + { text: "Manage project access with IdP groups", link: "/authentication/group-sync" },🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/.vitepress/config.ts` at line 305, Update the sidebar label string "IdP Group Sync" used in the config entry with link "/authentication/group-sync" so it matches the target page title "Manage project access with IdP groups" (i.e., change the visible text to that exact title) to ensure consistency between the sidebar and the destination page.docs/core-concepts/workspaces/overview.md (1)
10-10: Consider aligning tone with the rest of the docs page.Line 10’s closing phrase (“if that’s how you roll”) reads more casual than adjacent sections. A neutral phrasing would keep voice consistent.
Proposed wording
-The workspace is where your team gathers to work on projects, track progress, and get things done. You can create your own projects, invite others to join, and collaborate as a group, or just do your own thing if that’s how you roll. +The workspace is where your team gathers to work on projects, track progress, and get things done. You can create projects, invite others to join, and collaborate as a team.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/workspaces/overview.md` at line 10, The closing phrase in the sentence "The workspace is where your team gathers to work on projects, track progress, and get things done. You can create your own projects, invite others to join, and collaborate as a group, or just do your own thing if that’s how you roll." is too casual compared to the surrounding documentation; replace "or just do your own thing if that’s how you roll" with a more neutral alternative such as "or work independently if preferred" (or similar) so the tone matches the rest of the page; update the sentence in overview.md accordingly.docs/importers/csv.md (1)
20-35: Reduce duplicated schema rules to prevent docs drift.The allowed values/format rules are defined in both “Prepare your CSV” and “Imported fields.” Consider keeping one canonical schema section and linking to it from the other section so future updates stay consistent.
Also applies to: 76-85
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/importers/csv.md` around lines 20 - 35, The docs duplicate the allowed-values and format rules for columns (e.g., priority, start_date/target_date, state_group and description_html) across the "Prepare your CSV" and "Imported fields" sections; pick one canonical schema section (either "Prepare your CSV" or "Imported fields"), move the allowed-values/format rules (priority: urgent/high/medium/low/none; dates: YYYY-MM-DD; state_group: backlog/unstarted/started/completed/cancelled; description_html notes) into that single section, remove the duplicate rules from the other section, and replace the removed content with a short cross-reference/link to the canonical section so future edits update only one place.docs/importers/flatfile.md (1)
2-3: Make the page title explicitly Flatfile-specific.This page currently looks title-wise like the standard CSV importer page. A Flatfile-specific title/description would improve discoverability and reduce ambiguity in search/navigation.
Proposed doc wording tweak
-title: Import data from CSV file -description: Import work items from CSV files to Plane. +title: Import data with Flatfile CSV Importer +description: Import work items from CSV files to Plane using the Flatfile importer.Also applies to: 6-8
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/importers/flatfile.md` around lines 2 - 3, Update the page title and description to explicitly reference Flatfile (e.g., change "Import data from CSV file" to "Import data with Flatfile" and adjust the description to mention Flatfile's CSV import flow), and apply the same Flatfile-specific wording changes to the other title/description instances referenced around lines 6-8 so the page and its metadata clearly indicate this is the Flatfile importer documentation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/importers/flatfile.md`:
- Line 30: The documentation currently references the product tile label as
"Flatfile Importers" (the phrase in docs/importers/flatfile.md), but the UI uses
the singular "Flatfile Importer"; update the sentence that reads 'look for the
**Flatfile Importers** tile' to use the exact UI label "Flatfile Importer" so
the doc matches the UI verbatim and avoid user confusion.
- Line 54: Update the specified wording instances in docs/importers/flatfile.md:
replace “For very large datasets” with “For large datasets” (occurs at line
containing "That's it! Your CSV data..."), change “here's exactly what you can
transfer over” to “here's what you can transfer” (occurrence around the
transfers list), and change “originally created” to “created” (occurrence in
descriptions of source metadata); apply the same edits at the other noted
occurrences (the lines corresponding to 60 and 70).
---
Nitpick comments:
In `@docs/.vitepress/config.ts`:
- Line 305: Update the sidebar label string "IdP Group Sync" used in the config
entry with link "/authentication/group-sync" so it matches the target page title
"Manage project access with IdP groups" (i.e., change the visible text to that
exact title) to ensure consistency between the sidebar and the destination page.
In `@docs/core-concepts/workspaces/overview.md`:
- Line 10: The closing phrase in the sentence "The workspace is where your team
gathers to work on projects, track progress, and get things done. You can create
your own projects, invite others to join, and collaborate as a group, or just do
your own thing if that’s how you roll." is too casual compared to the
surrounding documentation; replace "or just do your own thing if that’s how you
roll" with a more neutral alternative such as "or work independently if
preferred" (or similar) so the tone matches the rest of the page; update the
sentence in overview.md accordingly.
In `@docs/importers/csv.md`:
- Around line 20-35: The docs duplicate the allowed-values and format rules for
columns (e.g., priority, start_date/target_date, state_group and
description_html) across the "Prepare your CSV" and "Imported fields" sections;
pick one canonical schema section (either "Prepare your CSV" or "Imported
fields"), move the allowed-values/format rules (priority:
urgent/high/medium/low/none; dates: YYYY-MM-DD; state_group:
backlog/unstarted/started/completed/cancelled; description_html notes) into that
single section, remove the duplicate rules from the other section, and replace
the removed content with a short cross-reference/link to the canonical section
so future edits update only one place.
In `@docs/importers/flatfile.md`:
- Around line 2-3: Update the page title and description to explicitly reference
Flatfile (e.g., change "Import data from CSV file" to "Import data with
Flatfile" and adjust the description to mention Flatfile's CSV import flow), and
apply the same Flatfile-specific wording changes to the other title/description
instances referenced around lines 6-8 so the page and its metadata clearly
indicate this is the Flatfile importer documentation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 28f8a228-3927-4c8a-8970-c0961dd2e8c4
📒 Files selected for processing (12)
docs/.vitepress/config.tsdocs/.vitepress/theme/components/Card.vuedocs/ai/pi-chat.mddocs/core-concepts/issues/plane-query-language.mddocs/core-concepts/projects/overview.mddocs/core-concepts/workspaces/overview.mddocs/importers/confluence.mddocs/importers/csv.mddocs/importers/flatfile.mddocs/importers/notion.mddocs/importers/overview.mddocs/workflows-and-approvals/workflows.md
💤 Files with no reviewable changes (2)
- docs/importers/confluence.md
- docs/importers/notion.md
| - If something's not right, you can click Back to adjust your field mapping. | ||
| - When you're ready, click **Submit** to import your data. | ||
|
|
||
| 11. That's it! Your CSV data is now imported into your Plane project. For very large datasets, the import might take a few minutes to process. |
There was a problem hiding this comment.
Tighten wording for concision and tone consistency.
Minor copy edits recommended:
- “For very large datasets” → “For large datasets”
- “here's exactly what you can transfer over” → “here's what you can transfer”
- “originally created” → “created”
Also applies to: 60-60, 70-70
🧰 Tools
🪛 LanguageTool
[style] ~54-~54: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...w imported into your Plane project. For very large datasets, the import might take a few m...
(EN_WEAK_ADJECTIVE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/importers/flatfile.md` at line 54, Update the specified wording
instances in docs/importers/flatfile.md: replace “For very large datasets” with
“For large datasets” (occurs at line containing "That's it! Your CSV data..."),
change “here's exactly what you can transfer over” to “here's what you can
transfer” (occurrence around the transfers list), and change “originally
created” to “created” (occurrence in descriptions of source metadata); apply the
same edits at the other noted occurrences (the lines corresponding to 60 and
70).
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/workspaces-and-users/manage-licenses.md`:
- Line 70: Replace the duplicated heading text "In Portal portal" with a single
clear title (e.g., "In Prime portal") in the markdown file; locate the heading
string "In Portal portal" and update it to the chosen title so the section
header is not duplicated or typo'd.
- Line 78: The markdown image URL in the line containing ""
is malformed due to a stray space before ".webp"; fix it by removing the space
so the path becomes
"https://media.docs.plane.so/activate-license/<filename>.webp#hero-tl" (or the
correct filename) ensuring the image filename and extension are contiguous;
update the markdown alt-texted image line accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3fc6cdbc-7f4c-4b0b-bdbe-f78eaa3fd4a6
📒 Files selected for processing (1)
docs/workspaces-and-users/manage-licenses.md
There was a problem hiding this comment.
♻️ Duplicate comments (1)
docs/importers/flatfile.md (1)
54-54:⚠️ Potential issue | 🟡 MinorTighten recurring wording in three spots for consistency.
The same copy nits previously flagged are still present:
- Line 54: “For very large datasets” → “For large datasets”
- Line 60: “here’s exactly what you can transfer over” → “here’s what you can transfer”
- Line 70: “originally created” → “created”
✍️ Suggested edits
-11. That's it! Your CSV data is now imported into your Plane project. For very large datasets, the import might take a few minutes to process. +11. That's it! Your CSV data is now imported into your Plane project. For large datasets, the import might take a few minutes to process. -When bringing your data from CSV into Plane, here's exactly what you can transfer over: +When bringing your data from CSV into Plane, here's what you can transfer: -| Created by | **Must be email addresses** - allows Plane to track who originally created the item | +| Created by | **Must be email addresses** - allows Plane to track who created the item |Also applies to: 60-60, 70-70
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/importers/flatfile.md` at line 54, Update the wording in docs/importers/flatfile.md to apply the three consistency edits: change "For very large datasets" to "For large datasets", change "here’s exactly what you can transfer over" to "here’s what you can transfer", and change "originally created" to "created"; locate and replace those exact phrases in the document (they appear near the CSV import summary and the transfer/creation descriptions) so the copy is consistent across the file.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/importers/flatfile.md`:
- Line 54: Update the wording in docs/importers/flatfile.md to apply the three
consistency edits: change "For very large datasets" to "For large datasets",
change "here’s exactly what you can transfer over" to "here’s what you can
transfer", and change "originally created" to "created"; locate and replace
those exact phrases in the document (they appear near the CSV import summary and
the transfer/creation descriptions) so the copy is consistent across the file.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 76bc7f49-0396-4525-9088-16f3c6149774
📒 Files selected for processing (1)
docs/importers/flatfile.md
sriramveeraghanta
approved these changes
Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit
New Features
Improvements
PtoNthenP.Documentation