chore: enable intake from project settings

[NarayanBavisetti]

chore:

• this pull request resolves the issue for enabling intake from project settings

Summary by CodeRabbit

• New Features

  • Enhanced project update and creation processes with improved handling of project states.
  • Introduced streamlined logic for managing view properties during updates.

• Bug Fixes

  • Implemented error handling for project creation to prevent conflicts with existing project names and workspaces.

• Improvements

  • Strengthened permission checks for project deletion to ensure only authorized users can delete projects.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes made to the ProjectViewSet class in apiserver/plane/app/views/project/base.py include modifications to the partial_update, create, and destroy methods. The partial_update method now incorporates a new variable, intake_view, simplifying the logic for view checks. The create method has been updated to facilitate bulk creation of default project states with error handling for existing project names. The destroy method enforces stricter permission checks before allowing project deletions.

Changes

File Path	Change Summary
apiserver/plane/app/views/project/base.py	- Updated partial_update method to simplify view checks and include intake_view.
	- Enhanced create method for bulk creation of default states and added error handling.
	- Modified destroy method to enforce permission checks for project deletion.

Possibly related PRs

• [WEB-1920] fix: project intake disabled validation #5161: Modifications related to project view conditions that may connect to intake_view handling.
• fix: intake issue #5813: Addresses issues in InboxIssueCreateRoot, potentially linking to project updates involving intake_view.
• [WEB-2709] chore: intake issue navigation improvement #5891: Navigation improvements for intake issues, relevant to project states and views.
• fix: intake loading #5966: Focuses on loading state of project settings, possibly related to enhanced project management functionalities.

Suggested labels

🧹chore

Suggested reviewers

• SatishGandham
• sriramveeraghanta

🐇 In the meadow, changes bloom,
A view refined, dispelling gloom.
With states created, projects thrive,
Permissions checked, we come alive!
A hop, a skip, to code we cheer,
For every update, we hold dear! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.