fix: attachment_count in issue pagination v2 endpoint

[gurusainath]

Summary

This fix addresses the issue where the attachment_count field was missing or incorrect in the issue pagination v2 endpoint.

Summary by CodeRabbit

• New Features
  • Enhanced issue retrieval with attachment count for each issue.
  • Conditional inclusion of the description field based on user request, defaulting to "false" if not specified.
• Bug Fixes
  • Improved handling of query parameters and response structure for better user experience.

[coderabbitai]

Walkthrough

The changes made in this pull request focus on enhancing the functionality of the IssuePaginatedViewSet class within the apiserver/plane/app/views/issue/base.py file. Key updates include the addition of an attachment_count annotation in the get_queryset method and a conditional check for the is_description_required parameter in the list method. These modifications improve the handling of attachments and refine the response structure based on user requests.

Changes

File Path	Change Summary
apiserver/plane/app/views/issue/base.py	- Updated list method in IssuePaginatedViewSet to add condition for is_description_required. - Updated get_queryset method in IssuePaginatedViewSet to include attachment_count annotation.

Possibly related PRs

• [WEB-2616] fix: issue widget attachment #5820: The changes in this PR involve fixing attachment functionality, which is directly related to the modifications made in the get_queryset method of the IssuePaginatedViewSet class that enhances attachment handling.

Suggested reviewers

• SatishGandham
• sriramveeraghanta

Poem

In the land of issues, where attachments play,
A count was added to brighten the day.
With descriptions now clear, and fields that align,
Our views are enhanced, oh how they shine!
Hopping along, we celebrate this feat,
For every small change makes our project complete! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c1a67cb and 97e9396.

📒 Files selected for processing (1)

• apiserver/plane/app/views/issue/base.py (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apiserver/plane/app/views/issue/base.py

---

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4e70e89 and c1a67cb.

📒 Files selected for processing (1)

• apiserver/plane/app/views/issue/base.py (2 hunks)

🧰 Additional context used

🔇 Additional comments (1)

apiserver/plane/app/views/issue/base.py (1)

758-766: LGTM on the attachment_count annotation

The addition of the attachment_count annotation correctly calculates the number of attachments for each issue and is consistent with the existing code patterns.