Product Goals
Just want to do it in the dashboard? See the guide: Set a product goal and follow it.
A product can have goals, such as “move every service to OIDC” or “retire the v1 payments API.” Each goal has ordered steps. OpenTremor checks each reviewed pull request against the active goals for its product. The result appears in the pull request comment and on the goal’s timeline.
A pull request never changes a goal or step status. You set a step’s status, or its measure does when no open findings remain. The check only reports what it saw (core ADR 0040).
Set a goal
Section titled “Set a goal”-
In the dashboard: Products → a product → Goals. Click New goal.
-
Enter the goal, describe what done looks like, and add steps in order. Only Active goals are checked on pull requests. A new goal starts as Draft.
-
Optionally, enter the Files that matter, one glob per line.
*matches across folders. A pull request that changes none of those files is not checked against that goal and costs nothing. -
Save the goal. Set each step’s status on the goal card as work progresses.
The same is available through /orgs/{org_id}/products/{product_id}/goals (API reference) and, for agents, the MCP tools list_goals, get_goal and update_goal_step. An agent that reads the active goals before it writes code can use them to guide its changes.
Creating and editing goals needs goals:manage (admins by default). Every member who can see products can read goals.
What a pull request gets
Section titled “What a pull request gets”After the analysis and agent-injection scan, OpenTremor makes one LLM call per pull request for all relevant active goals. The model reads:
- the goals and their steps;
- the pull request’s title, description and commit messages, newest commit first, up to about 4,000 characters, with merge and fixup commits skipped;
- the diff, with files matching a goal’s globs first.
For each goal, it returns advances, regresses or neutral, the step it touches, one sentence and up to three changed files. The comment gets a Goals section:
Advances Move to OIDC — step 2, checkout-api uses OIDC: the service now signs in with the OIDC client (
services/checkout/auth.py)
Non-neutral verdicts appear on the goal’s Pull requests timeline.
Everything the model reads from a pull request was written by its author, so the check is strict:
- A verdict must cite a changed file. A verdict with no file from the diff counts as neutral. A description that says “this completes step 3” does not prove it.
- Flagged text is left out. If the agent-injection scan flags the title, description or a commit message, that text is not sent to the model, and the comment says so.
- No verdict changes a step. Only you or a measure can do that.
Countable steps: measures
Section titled “Countable steps: measures”Some steps can be counted. For example, “No outbound call without a timeout” is done when no open finding remains for its rules. Give such a step a measure: one or more rule IDs and a minimum severity.
- The step card shows the number of open, needs-review and acknowledged findings for those rules in the product’s repositories.
- After a review on the product, a measured step whose count is zero is marked done, with done by its measure.
A step whose rules never had a finding is marked done at the first review. To establish the starting count, run a repository scan of the default branch first.
Guarded steps
Section titled “Guarded steps”Turn on Guard once done for a step that must not be undone. Once the step is done, a pull request that regresses it gets a needs-review finding. The commit status stays pending until someone acknowledges the finding or marks it a false positive.
A regression is either:
- a regresses verdict on that step; or
- for a step with a measure, an open finding for one of its rules in the pull request. This case needs no model call.
Guard is off by default. A pull request that does not regress a guarded step is not held.
With the Jira integration connected, Create in Jira on a goal creates an epic for the goal and one issue per step, in the product’s Jira target or, if none is set, the default target. On Jira Cloud, each issue’s parent is the epic. On Data Center, the issue names the epic in its text. You can also enter existing keys in the goal editor.
The Jira sync then:
- comments on a step’s issue for each pull request that advances or regresses it;
- moves the issue to Done when the step is done.
The sync works one way, as it does for findings. Moving an issue in Jira does not change the step.
Model and cost
Section titled “Model and cost”The check uses the review’s connection and model. To use another model, switch on Use a dedicated model in the dashboard under Products → Goal check, or call PUT /v1/orgs/{org_id}/goal-settings. Each call counts against the organization’s monthly LLM budget. If the budget is spent or the call fails, the comment says Goals not checked and the review continues.