Grove tracks delivery for you. When builders link their pull requests to a project, Grove reads the merged code and checks it against each outcome. You see the result on the project's page.
Delivery tracking needs GitHub connected to your workspace. A workspace admin connects it. See Connect GitHub.
The status card
Open a project's Overview. The Project status card shows:
The status, such as Planning. Click it to change it.
The time left to the target date, such as "18 days left."
A headline about the outcomes, such as "No work is linked to any of the two outcomes yet" or "All 3 outcomes are built and waiting on review."
One dot per outcome, colored by its tag.
Worth knowing: notes from Grove, such as a target that's close with nothing linked yet.
A timeline, from the day the project started, through Today, to the target date.
An initiative has the same card, called Initiative status.
Outcome tags
On the Scope tab, each outcome has a tag:
Tag | What it means |
Nothing linked | No work is linked to this outcome yet. |
Building | Work is linked and in progress. Or a builder says it's done, and Grove hasn't confirmed it yet. |
Ready for review | Grove read the merged code and finds the outcome done. Try it. |
Needs you | A builder says the outcome is done, but Grove's reading of the code doesn't agree. You decide. |
Done | Someone ticked the outcome's box. |
Click a tag to see why it says what it says. See Review shipped work and mark outcomes done.
The Delivery tab
On a project's Overview, click Delivery to see its pull requests. Filter them by In progress, Merged, Closed, or All. Each row shows:
What the pull request does, in plain words.
Its size: S, M, L, or XL.
Who opened it, and how long it has been in its state, such as "Open for 2 days."
Without GitHub connected, the tab says Track build status from GitHub. Admins see Connect GitHub. Other members are asked to contact an admin.
How a pull request gets linked
Builders link a pull request to a project in any of these ways:
They put the project ID, such as P-003, in the branch name or the pull request title.
They write "Part of P-003" in the pull request description.
Their coding agent adds a claims block that says which outcomes the pull request delivers.
If a pull request isn't linked, paste Part of P-003 into its description, with the right project ID.
How Grove checks the work
When a pull request merges, Grove reads the merged code. It doesn't look at what the builder claimed.
Grove checks each outcome against the code.
Grove sets each outcome's tag from what it found, and from what the builder claimed.
Grove never ticks an outcome done, and never sets a project to Built. You do that, after you've seen the work. See Review shipped work and mark outcomes done.