chore: add attachment in intake issue

[NarayanBavisetti]

Description

• added the patch request endpoint for the image upload in issue.

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

Summary by CodeRabbit

• New Features
  • Added a new URL endpoint for accessing specific issue attachments by their unique identifier
  • Enables more granular retrieval and manipulation of individual issue attachments within projects and workspaces

[coderabbitai]

Walkthrough

A new URL pattern has been added to the apiserver/plane/api/urls/issue.py file to enable accessing a specific issue attachment by its unique identifier (UUID). This addition provides a more granular route for retrieving or manipulating individual issue attachments within a specific workspace, project, and issue context.

Changes

File	Change Summary
apiserver/plane/api/urls/issue.py	Added a new URL pattern for accessing issue attachments by UUID

Possibly related PRs

• [WEB-2718] chore: issue attachment deletion #5903: Modifications to the IssueAttachmentV2Endpoint related to issue attachment handling
• feat: add issue attachment v1 endpoint  #6307: Enhancements to the IssueAttachmentEndpoint for managing issue attachments

Suggested labels

⚙️backend

Suggested reviewers

• pablohashescobar

Poem

🐰 A URL path, crisp and bright,
Attachments dancing in digital light
UUID in hand, we traverse with glee
Through workspaces, projects, issues free
A rabbit's route to data's delight! 🌈

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

apiserver/plane/api/urls/issue.py (1)

74-78: Maintain consistent URL naming pattern.

The collection endpoint uses name="attachment" while this endpoint uses name="issue-attachment". Consider using consistent naming:

     path(
         "workspaces/<str:slug>/projects/<uuid:project_id>/issues/<uuid:issue_id>/issue-attachments/<uuid:pk>/",
         IssueAttachmentEndpoint.as_view(),
-        name="issue-attachment",
+        name="attachment",
     ),

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f4af78c and 80f863f.

📒 Files selected for processing (1)

• apiserver/plane/api/urls/issue.py (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

🔇 Additional comments (1)

apiserver/plane/api/urls/issue.py (1)

74-78: LGTM! The URL structure follows REST conventions.

The new endpoint correctly implements the nested resource pattern and properly types all parameters.