See every Dart task next to the pull request delivering it
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.
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.
What does this prompt do?
- Puts every in progress Dart task next to the pull request that is supposed to be delivering it, so you can see whether the work is really moving
- Splits the board into three lanes: started with no pull request yet, waiting on review, and approved but still not merged
- Flags any card that has sat without activity longer than your threshold, which starts at two days and is yours to change
- Gives a full section to pull requests with no matching task at all, which is how untracked work stops hiding
What do I need to use this?
- A Dart workspace where your team keeps tasks in in progress statuses
- A GitHub account with access to the repositories you want on the board
- A Slack workspace, if you want to nudge reviewers straight from a card
- Ideally a habit of putting the task id in the pull request title or branch name, though you can always link a pair by hand
How can I customize it?
- Change the staleness threshold from the default two days to whatever your team considers stuck
- Choose which repositories the board covers, and add more as teams grow
- Switch between the lead view across every repository and a personal filter showing only your own tasks and review requests
FAQs
Does this move my task statuses automatically?
What happens if our pull requests do not mention the task id?
Is this only useful for engineering leads?
How does the board decide something is stale?
Can it cover more than one repository?
Related templates
Search creators for free, shortlist the best with your team, and spend an audit credit only when you decide someone is worth a closer look.
One screen showing invited, completed, and shortlisted counts for every open role, plus the stalled invites that have quietly gone nowhere.
Open one board each morning to see which of your facilities, suppliers and shipping lanes are sitting near trouble in the news right now.
Pick creators from your saved list and see their best and worst Instagram posts side by side, so your brief is built on what actually lands.
One screen where your hiring team watches every unscored candidate, reads the transcript alongside each answer, and scores and shortlists on the spot.
Drag every new company from your Harmonic saved searches through New, Tracking, Meeting and Passed, with a one click diligence brief on every card.
Stop trusting task statuses to tell you what shipped.
See in progress work and the pull requests meant to be delivering it on one board, with stale cards and untracked pull requests called out.