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 56 minutes and 38 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)
📝 WalkthroughWalkthroughThe pull request restructures the documentation sidebar navigation for work item types, converting a single link into a collapsed group with "Project-level" and "Workspace-level" sub-items. Documentation is updated to reflect workspace-level work item type management in Enterprise Grid and introduces a new comprehensive guide for workspace-level work item types. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 (2)
docs/core-concepts/workspaces/work-item-types.md (2)
8-8: Remove duplicate sentence.The sentence "This ensures consistency — a 'Bug' in one project has the same properties and structure as a 'Bug' in another" appears identically on both line 8 and line 16. Remove it from one location to avoid redundancy.
📝 Proposed fix (remove from line 16)
## How work item types work -Work item types are workspace-level entities. This means they're defined once by Workspace Admins and can be reused across any project in the workspace. This ensures consistency — a "Bug" in one project has the same properties and structure as a "Bug" in another. +Work item types are workspace-level entities. This means they're defined once by Workspace Admins and can be reused across any project in the workspace.Also applies to: 16-16
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/workspaces/work-item-types.md` at line 8, Remove the duplicate sentence "This ensures consistency — a 'Bug' in one project has the same properties and structure as a 'Bug' in another" so it only appears once in the document; locate the repeated string in the work item types doc (the identical sentence present twice) and delete the redundant instance, leaving the remaining occurrence intact.
148-153: Consider adding reassignment guidance.The delete section warns that "Existing work items of that type will need to be reassigned to another type" but doesn't explain how to do this. Consider adding a brief note or cross-reference on how users can bulk-update work item types (referencing the "Bulk update types" section above) before deletion.
📝 Suggested addition
Deleting a type removes it from the workspace library and from every project that imported it. Existing work items of that type will need to be reassigned to another type. + +To reassign existing work items before deleting a type, use the [bulk update](`#bulk-update-types`) feature to switch them to a different type. Before deleting, consider whether disabling the type would be a better option — it preserves existing work items while preventing new ones from being created.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/workspaces/work-item-types.md` around lines 148 - 153, Update the "Delete a work item type" section to include a brief instruction and cross-reference to the "Bulk update types" section: add a sentence after the warning "Existing work items of that type will need to be reassigned to another type" that tells Workspace Admins they can bulk-update work item types using the "Bulk update types" workflow and link to that section (or include the short steps) so users know how to reassign items before deletion; ensure the text mentions the "Delete a work item type" heading and the "Bulk update types" section to make the cross-reference clear.
🤖 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/core-concepts/issues/issue-types.md`:
- Line 8: The document inconsistently names the default work item type as `Task`
in the opening and `Issue` elsewhere; decide which is correct and make them
consistent by replacing all occurrences of the incorrect name (e.g., change "The
default type is called `Issue`" and "the work item type `Issue` is selected") to
the chosen canonical name (`Task` or `Issue`) and verify headings, examples, and
captions reference the same term (search for the phrases "default type",
"`Issue`", and "`Task`" and update `Issue`/`Task` instances accordingly).
- Line 108: The table row "| **URL** | A URL field for linking to external
resources. |" is missing the middle "Attributes" column causing markdown table
misalignment; update that row to include a placeholder or appropriate attributes
cell between the pipes (e.g., "| **URL** | [attributes or '—'] | A URL field for
linking to external resources. |") so the row matches the three-column structure
used by other rows and resolves the markdownlint error.
---
Nitpick comments:
In `@docs/core-concepts/workspaces/work-item-types.md`:
- Line 8: Remove the duplicate sentence "This ensures consistency — a 'Bug' in
one project has the same properties and structure as a 'Bug' in another" so it
only appears once in the document; locate the repeated string in the work item
types doc (the identical sentence present twice) and delete the redundant
instance, leaving the remaining occurrence intact.
- Around line 148-153: Update the "Delete a work item type" section to include a
brief instruction and cross-reference to the "Bulk update types" section: add a
sentence after the warning "Existing work items of that type will need to be
reassigned to another type" that tells Workspace Admins they can bulk-update
work item types using the "Bulk update types" workflow and link to that section
(or include the short steps) so users know how to reassign items before
deletion; ensure the text mentions the "Delete a work item type" heading and the
"Bulk update types" section to make the cross-reference clear.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7c8e86f9-f486-4ba0-bf1d-323c72d0ba22
📒 Files selected for processing (4)
docs/.vitepress/config.tsdocs/core-concepts/issues/issue-types.mddocs/core-concepts/workspaces/work-item-types.mddocs/workspaces-and-users/billing-and-plans.md
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/core-concepts/workspaces/work-item-types.md (1)
14-22: Remove duplicate explanation of consistency.Lines 16 and 8 contain the exact same explanation: "This ensures consistency — a 'Bug' in one project has the same properties and structure as a 'Bug' in another." Since this concept is already introduced at the top of the page, consider removing the duplicate from line 16 or rephrasing it to avoid repetition.
♻️ Proposed revision to reduce redundancy
-Work item types are workspace-level entities. This means they're defined once by Workspace Admins and can be reused across any project in the workspace. This ensures consistency — a "Bug" in one project has the same properties and structure as a "Bug" in another. +Work item types are workspace-level entities defined once by Workspace Admins and reused across any project in the workspace.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/workspaces/work-item-types.md` around lines 14 - 22, The paragraph under "## How work item types work" repeats the sentence "This ensures consistency — a 'Bug' in one project has the same properties and structure as a 'Bug' in another."; remove the duplicate instance (or rephrase it) so the concept appears only once—keep the initial occurrence and either delete the second occurrence in the middle paragraph or replace it with a short transitional phrase about reuse across projects to avoid redundancy while preserving meaning.
🤖 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/core-concepts/workspaces/work-item-types.md`:
- Line 36: Replace every instance of the incorrect label "Work item Types" with
the title-cased "Work Item Types" throughout the document; locate occurrences in
the menu/tab references (the string "Workspace Settings > Work item Types" and
standalone "Work item Types" headings/mentions) and update them to "Workspace
Settings > Work Item Types" and "Work Item Types" respectively so all Settings
references follow consistent title case.
---
Nitpick comments:
In `@docs/core-concepts/workspaces/work-item-types.md`:
- Around line 14-22: The paragraph under "## How work item types work" repeats
the sentence "This ensures consistency — a 'Bug' in one project has the same
properties and structure as a 'Bug' in another."; remove the duplicate instance
(or rephrase it) so the concept appears only once—keep the initial occurrence
and either delete the second occurrence in the middle paragraph or replace it
with a short transitional phrase about reuse across projects to avoid redundancy
while preserving meaning.
🪄 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: 00f33b69-d433-4430-b518-ad8df6655fd3
📒 Files selected for processing (3)
docs/.vitepress/config.tsdocs/core-concepts/issues/issue-types.mddocs/core-concepts/workspaces/work-item-types.md
🚧 Files skipped from review as they are similar to previous changes (2)
- docs/core-concepts/issues/issue-types.md
- docs/.vitepress/config.ts
|
|
||
| > **Role**: Workspace Admin | ||
|
|
||
| 1. Go to **Workspace Settings > Work item Types**. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for other instances of work item type capitalization patterns to check consistency
rg -n -i "work item type" docs/ -g '*.md' | head -20Repository: makeplane/docs
Length of output: 2959
🏁 Script executed:
#!/bin/bash
# Read the full file to see all instances and context
cat -n docs/core-concepts/workspaces/work-item-types.md | head -120Repository: makeplane/docs
Length of output: 8333
🏁 Script executed:
#!/bin/bash
# Check if there are any style guides or documentation conventions
find docs -name "*style*" -o -name "*guide*" -o -name "*convention*" | head -10Repository: makeplane/docs
Length of output: 89
🏁 Script executed:
#!/bin/bash
# Check how other Settings menu items are capitalized in the docs
rg -n "Settings >" docs/ -g '*.md' | grep -E "(Settings >|> [A-Z])" | head -15Repository: makeplane/docs
Length of output: 1942
Fix capitalization of "Work Item Types" in Settings references.
The file uses "Work item Types" (mixed case with capital W, lowercase i, capital T) when referencing Settings menu items and tabs. This should be "Work Item Types" (title case) to match:
- Standard UI element naming conventions
- Other Settings references in the docs (e.g., "Workspace Settings > Members", "Project Settings > Members & Teamspaces")
- Capitalization patterns for proper nouns in menu paths
Update lines 36, 39, 47, 77, and 105 from "Work item Types" to "Work Item Types".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/core-concepts/workspaces/work-item-types.md` at line 36, Replace every
instance of the incorrect label "Work item Types" with the title-cased "Work
Item Types" throughout the document; locate occurrences in the menu/tab
references (the string "Workspace Settings > Work item Types" and standalone
"Work item Types" headings/mentions) and update them to "Workspace Settings >
Work Item Types" and "Work Item Types" respectively so all Settings references
follow consistent title case.
1 participant
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit