Pensero scores every merged pull request (merge request), whatever branch it targets. Commits pushed directly to a branch, without a pull request, are scored only on the repository's default branch (see Pull requests and trunk-based development). Tracked branches let you also count direct commits on other long-lived branches, so teams working there get credit for it now rather than months later.
When to use it
Track any branch where people push commits directly and that will not be merged into the default branch for a while, or ever. For example:
long-running integration or migration branches
customer-specific or pilot branches
proofs of concept (PoCs), prototypes and demos
any other long-lived branch where your team does real work
Short-lived feature branches don't need tracking: their work is scored through the pull request that merges them.
Tracking only matters for trunk-based work. Pensero already syncs every pull request (merge request), whatever branch it targets. Tracking a branch adds only the commits pushed directly to it, without a pull request. If a team works on a branch through pull requests, you don't need to track it.
What gets counted
Direct commits on a tracked branch are scored as delivery, just like direct commits on the default branch.
Commits the default branch already holds are not counted again, for example commits brought in when the branch was created or when the default branch is merged into it.
When you start tracking a branch, Pensero imports its past work from its first own commit, within your organization's history range, and then keeps it up to date.
Availability
Tracked branches are available on the Enterprise plan and are currently in Beta. If you don't see Tracked branches under Organization settings, contact Pensero support to enable it.
There is no limit on how many branches you can track per repository.
Turn it on
You need Admin permissions to change this setting.
Go to Organization > Tracked branches
Turn on Track extra branches
Once it is on, admins and managers can choose which branches to track in each repository.
Track a branch
Open the repository:
admins: go to Integrations, select your Git provider and select the repository
managers: open your team's Repositories tab and select the repository
In the Tracked branches section, type in Find a branch to track and select the branch from the list
The list shows the repository's branches from your Git provider. The default branch is always tracked, so it doesn't appear in the list.
Each tracked branch then shows:
Sync progress: "Waiting for first sync", "Backfilling" with a percentage, or "Ingested up to" a date
Impact: points, people and direct-commit PRs counted from the branch
A hint when the branch was merged into the default branch or has had no commits for a while, suggesting you stop tracking it
Below the list, Tracking history shows who started or stopped tracking each branch, and when.
Stop tracking a branch
In the Tracked branches section, click the × next to the branch and choose one of two options:
Keep history: new commits on the branch are no longer imported. The work already counted stays, with its points. Use this when the branch's work is finished, for example the work on it ended or the branch was merged.
Remove history: for a branch tracked by mistake. Pensero stops tracking it and removes the productivity it generated. The confirmation shows how many points and people are affected. To confirm, type the branch name. This cannot be undone. Real pull requests targeting the branch are not affected.
You can start tracking a branch again at any time.
If an admin turns off Track extra branches, Pensero stops importing all tracked branches but keeps the work already counted. Repositories that still have tracked branches keep showing the section, so you can still remove them.
Filters
Extra tracked branches column, in the repositories list under Integrations (Beta): the number of branches tracked in each repository besides the default branch. Use the Extra tracked branches ≥ filter to show only repositories with at least that many, for example ≥ 1 to list every repository with a tracked branch.
Type filter, on a repository's pull requests list: choose Pull requests or Direct commits. Combine it with the Target branch filter to see the work counted from a specific tracked branch.
Extra tracked branch criteria, in the What step of a cohort: count only the work from one or more tracked branches, or leave it out. See below.
Direct commits counted from a tracked branch show an Extra tracked branch badge with the branch name in work item lists and details.
Filter by tracked branch in cohorts
Use a cohort to see, for example, the work done on one tracked branch, or all work except tracked branches.
Click the selector at the top of the page (for example All 4 people), open the Cohorts tab and create a cohort, or edit one
Under 2 · What, click Select criteria and choose Extra tracked branch
Choose the operator:
Is any of: count only work from the branches you select
Is not: count all work except the work from the branches you select
Click Options and select one or more branches. Each branch shows as branch • repository, so branches with the same name in different repositories are separate.
Name the cohort and click Add cohort. Pensero applies it to the page.
1 · Who still chooses the people. 2 · What only limits which of their work is counted. Leave 2 · What empty to count all work.
The Extra tracked branch criteria appears only when your organization tracks at least one branch, and it lists only tracked branches. It matches the direct commits counted from those branches and any pull requests that target them.
To filter by all tracked branches at once, or to compare with the default branch, use the Branch type criteria (Default branch, Extra tracked branch, Other branch): see Filter by branch type.