feat(webapp): link to task-specific test page from filtered runs table by 0ski · Pull Request #2741 · triggerdotdev/trigger.dev

0ski · 2025-12-04T10:40:27Z

When viewing runs filtered to a single task, the "Create a test run" and "Run a test" buttons now navigate directly to the task-specific test page instead of the generic test page.

This improves UX by pre-populating the test form with the filtered task, saving users from having to manually select it again.

✅ Checklist

I have followed every step in the contributing guide
The PR title follows the convention.
I ran and tested the code works

Screenshots

When viewing runs filtered to a single task, the "Create a test run" and "Run a test" buttons now navigate directly to the task-specific test page instead of the generic test page. This improves UX by pre-populating the test form with the filtered task, saving users from having to manually select it again.

changeset-bot · 2025-12-04T10:40:31Z

⚠️ No Changeset found

Latest commit: 2dc3a2a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

coderabbitai · 2025-12-04T10:40:41Z

Walkthrough

This change modifies the TaskRunsTable component to conditionally select navigation paths based on filtered tasks. A new import of v3TestTaskPath is added, followed by two local variables that determine whether exactly one task is filtered and accordingly select either a task-specific or general test path. Hard-coded path references in two LinkButton components are replaced with this conditional path variable.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Verify v3TestTaskPath import is correctly resolved from the pathBuilder utility
Confirm the conditional logic correctly identifies single-task filters and selects the appropriate path
Ensure both LinkButton instances are properly updated to use the new testPath variable
Check that the path behavior is correct for edge cases (no filters, multiple tasks filtered, single task filtered)

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run `@coderabbitai generate docstrings` to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: linking to task-specific test page from filtered runs table, which matches the primary objective of the changeset.
Description check	✅ Passed	The description covers the key sections: it explains the change, its benefit to UX, includes a completed checklist, and provides a screenshot. All required template sections are present and adequately filled.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch oo/feat-dashboard-ui-improvements

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

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

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (1)

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx (1)
568-570: testPath derivation correctly targets task‑specific vs generic test pages

The singleTaskFromFilters + testPath logic cleanly captures “exactly one task filter → task‑specific test page, otherwise generic test page”, which matches the PR objective and keeps the branching localized to BlankState. Functionally this looks solid.

As a small optional tidy‑up, you could reuse the destructured tasks instead of filters.tasks to avoid repeating the property access:
-  const singleTaskFromFilters = filters.tasks.length === 1 ? filters.tasks[0] : null;
+  const singleTaskFromFilters = tasks.length === 1 ? tasks[0] : null;
Behavior would remain identical.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 117b1d5 and 2dc3a2a.

📒 Files selected for processing (1)

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx (4 hunks)

🧰 Additional context used

📓 Path-based instructions (6)

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Use types over interfaces for TypeScript
Avoid using enums; prefer string unions or const objects instead

Files:

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx

{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use zod for validation in packages/core and apps/webapp

Files:

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use function declarations instead of default exports

Files:

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx

apps/webapp/app/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

Access all environment variables through the env export of env.server.ts instead of directly accessing process.env in the Trigger.dev webapp

Files:

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx

apps/webapp/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

apps/webapp/**/*.{ts,tsx}: When importing from @trigger.dev/core in the webapp, use subpath exports from the package.json instead of importing from the root path
Follow the Remix 2.1.0 and Express server conventions when updating the main trigger.dev webapp

Files:

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx

**/*.{js,ts,jsx,tsx,json,md,css,scss}

📄 CodeRabbit inference engine (AGENTS.md)

Format code using Prettier

Files:

apps/webapp/app/components/runs/v3/TaskRunsTable.tsx

🧠 Learnings (5)