[DEV-103] Show tracker task description on run details and link runs to their tracker ticket - #91
Open
danii1 wants to merge 1 commit into
Open
[DEV-103] Show tracker task description on run details and link runs to their tracker ticket#91danii1 wants to merge 1 commit into
danii1 wants to merge 1 commit into
Conversation
…s and link runs to their tracker ticket
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task: DEV-103
Summary: Show tracker task description on run details and link runs to their tracker ticket
Implementation Details
I have a full picture now. Let me set up a plan and check remaining pieces (dashboard-api tests, docs).
Now implementing. Starting with backend: new
ticket-url.tsderivation module.Let me simplify that module — the builder map is awkward:
Now the run-recorder changes — description snapshot column, ticket metadata on
RunMeta, and asetRunTicket/recordRunTickethelper:Now the
createRuninsert and the new store method:Now the row mapping and module-level helper:
Now add the description-markdown builder to
TaskFormatter:I made an editing mistake — let me check and fix:
Now wire it into the pipeline in
index.ts:Now add the import and the description snapshot after
formatTaskDetails:Now update
dashboard-api.tsto keep the list payload light while detail returns full description:Backend done. Now the frontend —
api.tstype first, then new components:Now the
TaskDescriptioncomponent with markdown rendering, truncation, and placeholder:Now wire both into
RunDetailView:Now the runs list work cell — make it use
TicketKeyfor list/detail consistency:Now tests. Backend first — ticket URL derivation and run-recorder coverage:
Now extend
run-recorder.test.tswith ticket/description coverage:Now the UI component tests, following the
RunResult.test.tsxpattern:Now run the relevant test suites and typechecks:
All 48 dashboard-ui tests pass (including the 8 new ones). Now the code package tests:
The failure is my test expecting strict no-clobber;
COALESCEpreserves existing values only against null updates (which is what "cannot erase" means). Fixing the test to match the actual semantics:All green. Now format, lint, typecheck:
Now update the user-facing docs (
docs/code/dashboard.md):Final verification — full workspace build plus re-run of both affected test suites:
DEV-103 is implemented. Summary:
Backend (
@getdevintern/code)src/lib/ticket-url.ts(new): derives ticket web URLs from tracker config + key for Jira, GitHub, GitLab, Azure DevOps, Asana, and Trello; returnsundefinedfor Linear (needs org slug), markdown files, synthetic scheduled keys, or missing config — so the UI can fall back to plain text.run-recorder.ts:RunMetagainsticketKey/ticketUrl(persisted atcreateRun); additivetask_description TEXTmigration (same pattern asattempt/ticket_key); newsetRunTicket/recordRunTicketsnapshot the description (null-safe viaCOALESCE, blank→null, capped at 20 000 chars likeMAX_DETAIL_LENGTH).index.ts:beginRunrecords the derived URL (skipped for markdown/scheduled runs); afterformatTaskDetails, the ticket description is snapshotted at run start via newTaskFormatter.buildTaskDescriptionMarkdown(reuses rendered-HTML → turndown and ADF conversion paths used by prompts).dashboard-api.ts:/api/runs/:idserves the snapshot;/api/runsstrips it to keep the 5-second polling payload light.Frontend (
@devintern/dashboard-ui)TicketKeycomponent (linked/new-tab vs plain-text fallback) used by both the run detail header and the runs-list "Work" cell — consistent behavior in both views.TaskDescriptioncard on run detail: markdown rendering, explicit "No description provided." placeholder, >1500-char collapse with show more/less; hidden entirely for non-ticket runs (PR mentions).Verification: 1002 code tests + 48 dashboard-ui tests pass (18 new: URL derivation, persistence/capping/migration, API passthrough, linked/unlinked keys, placeholder/truncation); build, lint, format, and typecheck all clean. Docs updated in
docs/code/dashboard.md.This PR was automatically created by @devintern/code