Summary
- Adds a `pipeline_id` column to the `todos` table to store the specific pipeline that triggered a `build_failed` todo
- Updates the `build_failed` todo body to display up to 3 failed job names (e.g. `rspec, jest, rubocop and 2 more`), replacing the generic merge request title
- Updates the todo target URL to navigate directly to the specific pipeline that failed (e.g. `/-/pipelines/123`) instead of the MR's pipelines tab (`/-/merge_requests/123/pipelines`)
- Updates the Todos Vue app to render the failed job names in the todo item body
How it works
When a CI build fails on the head pipeline of a merge request, `AddTodoWhenBuildFailsService` now passes the pipeline object through the `TodoService#merge_request_build_failed` call chain and stores it as `pipeline_id` on the created `Todo` records.
The `Todo#body` method now returns a comma-separated list of failed job names when a pipeline is associated, truncating to 3 names with an "and N more" suffix when there are more. The `Todo#target_url` method now returns the specific pipeline URL when a pipeline is associated, falling back to the existing pipelines tab URL for older todos without a `pipeline_id`.
The `todo_item_body.vue` component uses the `body` field (already present in the GraphQL fragment) to render the job names alongside the "The pipeline failed" message, e.g. `The pipeline failed: rspec, jest, rubocop.`. It falls back to the generic message for older todos without job name data.
Changelog
- Updated `build_failed` todo to list failed job names (up to 3, then truncated)
- Updated `build_failed` todo destination to link to the specific failed pipeline
- Updated Todos frontend to display failed job names in the todo item body
Screenshots
| Before | After |
|---|---|
| - |
 |