[WEB-2699]chore: added issue count for upcoming cycles

[vamsikrishnamathala]

Description

Added issue count for upcoming cycles

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

Screenshots and Media

References

WEB-2699

Summary by CodeRabbit

• New Features

  • Introduced a new UI element that displays the total number of issues associated with a cycle, conditionally shown based on the cycle's status.
  • Added a LayersIcon to enhance the visual representation of the issue count.

• Bug Fixes

  • Improved the logic for displaying the issue count based on the cycle's status.

[coderabbitai]

Walkthrough

The pull request modifies the CycleListItemAction component in the web application, introducing a new UI feature that conditionally displays the total number of issues for cycles with "draft" or "upcoming" status. By utilizing the useMemo hook, the component now calculates and renders an issue count with a LayersIcon, enhancing the visual information about cycle-related issues without changing the component's core functionality.

Changes

File	Change Summary
web/core/components/cycles/list/cycle-list-item-action.tsx	- Added useMemo hook to derive showIssueCount variable - Introduced conditional rendering of issue count with LayersIcon - Updated import statements to include LayersIcon from @plane/ui

Possibly related PRs

• fix: moved dropdowns to chart component + added pending icon #5824: Introduces new icon and UI component modifications
• [WEB-2626] chore: removed the deleted issue's count #5837: Backend changes related to deleted issues
• [WEB-2769]fix: transfer cycles mutation issue #6200: Mutation issue in cycle transfers
• [WEB-2878]fix: draft creation #6230: Optimization of draft creation process

Suggested labels

🧹chore

Suggested reviewers

• SatishGandham
• sriramveeraghanta
• gurusainath

Poem

🐰 Cycles spin, issues bloom bright,
Layers of work come into sight,
Draft and upcoming, numbers gleam,
A rabbit's UI design supreme!
Code evolves with playful might 🚀

---

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/cycles/list/cycle-list-item-action.tsx (1)

229-235: Consider fallback handling for total_issues.
While conditionally rendering the issue count is a clear addition, ensure that total_issues reliably holds a valid numeric value. For instance, consider displaying “0” or hiding the count if the value is null or undefined.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ea78c2b and 56e1dd4.

📒 Files selected for processing (1)

• web/core/components/cycles/list/cycle-list-item-action.tsx (3 hunks)

🔇 Additional comments (3)

web/core/components/cycles/list/cycle-list-item-action.tsx (3)

3-3: Good use of useMemo.
Using useMemo for performance optimization is appropriate here, as it prevents unnecessary re-computations of derived values.

---

11-20: Imports are consistent with the new LayersIcon usage.
All imported modules appear relevant to the newly introduced features, and there are no apparent redundant imports.

---

78-78: Clear conditional logic for drafts and upcoming cycles.
The showIssueCount variable effectively checks if the cycle status is “draft” or “upcoming,” aligning with the intended design.