perf(ui): look up cycle/module names via maps on the issue list

[cavidelizade]

Summary

cycleName/moduleName on the work-item list did a linear cycles.find / modules.find for every row, and they're called a few times per row, so a large list was O(rows x cycles) per render.

Linked issues

Refs #345 (a focused slice)

Type of change

• Performance (perf:)

Surface

• UI (apps/web/)

What changed

Build id -> name maps once per render and look up in O(1), the same pattern the file already uses for stateById/labelById. Plain const rather than useMemo because this sits after the component's early returns.

Scope note

Issue #345 is broader (memoizing the Row/Card components and lifting drag/resize state out of the row subtree so the whole list doesn't re-render on hover/resize). That's a larger, riskier change I've left for a separate PR; this one is the safe, self-contained slice.

Test plan

• npm run typecheck + npm run lint pass

AI assistance

• AI tools were used, tool(s): Claude Code (Opus 4.8), commits carry a Co-Authored-By: trailer

[coderabbitai]

Warning

Review limit reached

@cavidelizade, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5bd0de9e-23a6-46f7-9163-f793d25f4c26

📥 Commits

Reviewing files that changed from the base of the PR and between 61bc903 and a559e6b.

📒 Files selected for processing (1)

• apps/web/src/pages/IssueListPage.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

_{Comment @coderabbitai help to get the list of available commands.}