[WEB-2880] chore: project detail response updated

[anmolsinghbhatia]

Description

This PR includes following changes:

• Updated the project detail response by adding completed_issues.

Type of Change

• Code refactoring

References

[WEB-2880]

Summary by CodeRabbit

• New Features
  • Introduced a new property, completed_issues, to the project interface for enhanced project tracking.
  • Enhanced the ProjectDropdown component with a new fallback icon, Briefcase, for improved user experience when no project icons are available.

[coderabbitai]

Walkthrough

The pull request introduces a new property completed_issues to the IProject interface in the project type definitions. This numeric property is added to the existing set of attributes that describe a project. Additionally, the ProjectDropdown component is updated with a new icon import and modified logic to display a fallback icon when no project values are present.

Changes

File	Change Summary
packages/types/src/project/projects.d.ts	Added completed_issues: number; to IProject interface
web/core/components/dropdowns/project.tsx	Added import for Briefcase icon and modified getProjectIcon function to include a fallback icon

Possibly related PRs

• fix: improvements for project types. #5857: The changes in this PR involve updating the ProjectDropdown component to use the TProject type instead of IProject, which may relate to the new completed_issues property added to the IProject interface in the main PR.
• [WEB-2743] chore: restrict sub-issue to have different project id than parent #5981: This PR introduces a restriction on sub-issues to ensure they belong to the same project as their parent issue, which is relevant to the IProject interface changes in the main PR.
• [WEB-2817] fix: creating a new sub-issue from workspace level #6169: This PR addresses a bug related to the project ID used when creating new sub-issues, which directly relates to the project management context of the IProject interface modified in the main PR.

Suggested labels

🌟enhancement

Suggested reviewers

• sriramveeraghanta
• SatishGandham

Poem

🐰 A new property hops into view,
Counting issues, both old and new.
completed_issues joins the dance,
Tracking progress with just a glance,
In the project's type declaration! 🚀

---

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)

web/core/components/dropdowns/project.tsx (1)

146-153: LGTM: Improved UX with fallback icon

The addition of a fallback Briefcase icon when no projects are selected improves the user experience by providing clear visual feedback. The implementation is clean and maintains proper type safety.

Minor suggestion: Consider aligning the fallback icon size with the Logo component size for consistency.

-            <Briefcase className="size-3 text-custom-text-300" />
+            <Briefcase className="size-3.5 text-custom-text-300" />

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 370409a and 8069c22.

📒 Files selected for processing (1)

• web/core/components/dropdowns/project.tsx (2 hunks)

🔇 Additional comments (2)

web/core/components/dropdowns/project.tsx (2)

4-4: LGTM: Import statement follows existing pattern

The addition of the Briefcase icon import is clean and consistent with the existing icon imports.

---

Line range hint 1-153: Verify relationship with PR objective

The changes in this file appear to be UI improvements, but their relationship to the PR's objective of adding completed_issues to the project detail response is unclear. Could you clarify:

1. Are there other files that implement the completed_issues feature?
2. How do these UI changes support the display of completed issues?

Let's check for other related changes: