See every Dart task next to the pull request delivering it

By General Input

A board that joins in progress Dart tasks to their GitHub pull requests, so leads can see where delivery is actually stuck instead of trusting statuses.

Integrations

  • Dart
  • GitHub
  • Slack

Type

App

Categories

  • Engineering
  • Operations

I want a delivery board that puts every in progress Dart task next to the GitHub pull request that is supposed to be delivering it, so my engineering leads can see where work is actually stuck instead of trusting task statuses. This is a read first review board, not an automatic sync.

Let me configure which GitHub repositories the board covers, and a staleness threshold in days that defaults to 2. Persist both settings in the app so they survive between sessions and apply on every load.

Read the Dart side with List Tasks filtered to the active, in progress statuses in my workspace, and use Get Task when a card needs fuller detail such as the assignee, the current status and the last update time.

Read the GitHub side with List Pull Requests across each configured repository, Get a Pull Request for the merge state of a specific pull request, and List Pull Request Reviews to see who has already reviewed and who was requested but has not responded. Use Search Issues and Pull Requests to locate the pull request that mentions a given Dart task id when the naming convention did not surface a match.

Match a Dart task to a pull request by looking for the Dart task id in the pull request title or in the head branch name. When the convention was not followed, let me manually link a task and a pull request from the board, and remember that link in the app so it persists across refreshes and later visits.

The board has three lanes. First, work marked in progress in Dart with no pull request opened yet. Second, pull requests waiting on review, meaning open with no approving review yet or with requested reviewers still outstanding. Third, pull requests that are approved but still not merged.

Give real estate to a fourth section listing open pull requests with no matching Dart task at all. This is how untracked work gets found and it is the highest value part of the board for an engineering manager, so give it a proper panel rather than burying it in a tab or a footer.

Each card shows the Dart task title and assignee, the pull request state and review state, and the number of days since the last activity. Flag anything past the staleness threshold visually so stale cards stand out at a glance, and let me order each lane by days since last activity.

From a card I want three actions. Update Task to move the Dart status when the board shows reality has already moved on, for example a task still marked in progress whose pull request merged days ago. Create Comment to leave a note on the Dart task. And a Slack nudge to a reviewer using Send a Message, opening a direct message conversation with that person when I do not already have one. Each of these is a manual action I choose on a card, never something the app performs on its own.

Support two views. A lead view across all configured repositories, and a personal filter where an engineer sees only their own assigned Dart tasks and the pull requests where their review has been requested.

To be clear about scope: this app must not automatically move Dart statuses when pull requests open, merge or close. The value is the joined view, the stale work and the untracked pull requests, with any status change staying a deliberate choice made by the person reading the board.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes