[WEB-3704] fix: sub work item

[anmolsinghbhatia]

Description

This PR fix sub work item rendering issue.

Type of Change

• Bug fix

References

[WEB-3704]

Summary by CodeRabbit

• Refactor
  • Enhanced the way issue details are retrieved and displayed within the issues list.
  • Simplified the data fetching process to ensure sub-issue information appears consistently.
  • This update streamlines internal processing while maintaining a stable and clear user experience.

[coderabbitai]

Walkthrough

The pull request modifies the IssueList component by changing the invocation of the useIssueDetail hook. The hook call now omits the previously provided issueServiceType argument, which shifts the method of acquiring issue details. The destructured assignment for subIssuesByIssueId remains unchanged, and no public or exported entity declarations were altered.

Changes

File Path	Change Summary
web/core/components/issues/.../issues-list.tsx	Removed the issueServiceType argument from the useIssueDetail hook call in the IssueList component.

Sequence Diagram(s)

sequenceDiagram
    participant IL as IssueList Component
    participant UDH as useIssueDetail Hook
    participant DS as Data Service

    IL->>UDH: Call useIssueDetail()
    UDH->>DS: Implicitly fetch issue details
    DS-->>UDH: Return details data
    UDH-->>IL: Provide { subIssuesByIssueId }

Loading

Possibly related PRs

• [WEB-3139] fix: sub-issue visibility #6410: This PR also involves changes to the useIssueDetail hook, indicating a direct relationship at the code level.

Suggested labels

🐛bug, 🌐frontend

Suggested reviewers

• sriramveeraghanta
• gurusainath

Poem

In the realm of code, I hop with glee,
Revising hooks, simple as can be.
The argument is gone, a cleaner flight,
Data flows smooth as day turns night.
With whiskers twitching, I celebrate each byte!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2bfe4d6 and dc3e9c2.

📒 Files selected for processing (1)

• web/core/components/issues/sub-issues/issues-list.tsx (1 hunks)

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

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

🔇 Additional comments (1)

web/core/components/issues/sub-issues/issues-list.tsx (1)

41-43:

Details

❓ Verification inconclusive

Removed unnecessary issueServiceType parameter from useIssueDetail hook.

The change aligns with the PR objective to fix sub work item rendering issues. By removing the issueServiceType parameter from the hook call, the component now lets the hook determine the service type internally, which should resolve the rendering inconsistencies mentioned in WEB-3704.

I recommend verifying that:

1. The useIssueDetail hook correctly handles being called without parameters
2. This change doesn't affect other places where subIssuesByIssueId data is consumed

---

🏁 Script executed:

#!/bin/bash
# Check if useIssueDetail hook is implemented to handle being called without parameters
echo "Checking useIssueDetail hook implementation..."
cat $(fd --type f --glob "**/hooks/store.ts" --no-ignore) 2>/dev/null || cat $(fd --type f --glob "**/hooks/store/index.ts" --no-ignore) 2>/dev/null || fd --type f --glob "**/hooks/**/useIssueDetail.ts*" --no-ignore

# Check if there are other instances of useIssueDetail being called with issueServiceType
echo -e "\nChecking other usages of useIssueDetail with parameters..."
rg "useIssueDetail\(" --type ts --type tsx

Length of output: 368

---

Action: Verify that the useIssueDetail hook is fully parameter-agnostic and its downstream data remains consistent

The change to remove the issueServiceType parameter appears to align with the PR's goal (WEB-3704) of fixing sub work item rendering issues. However, please confirm the following:

• Ensure that the useIssueDetail hook correctly handles being called with no parameters.
• Verify that no other parts of the codebase depend on explicitly passing the issueServiceType and that all consumers of subIssuesByIssueId continue to function as expected.

Please perform additional manual or script-based verification, especially given the earlier low-quality output when checking for usages.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[makeplane]

Pull Request Linked with Plane Work Items

• [WEB-3704] When accessed Epic via browse URL , linked work item doesn't display

Comment Automatically Generated by Plane