Tuleap

Tuleap exposes several object types: trackers (configurable containers for stories, tasks, bugs, and epics), sprints, projects, Git repositories, and users. Because Tuleap trackers are fully customizable per organization, the fundamental unit of work is the artifact — an instance of a tracker. This integration focuses on artifacts and sprint-level aggregations, which together cover the core concerns of engineering performance management. Six KPIs were retained, selected against three criteria: ability to attribute to an owner via the contributor semantic, resistance to gaming, and balance between leading and lagging indicators.

Delivery throughput and velocity

Artifacts Closed counts the number of work items a user completed in the period, regardless of type. Average Cycle Time measures the average elapsed time between artifact creation and closure for the same user. These two indicators anchor the delivery analysis and are designed to be read together. A high Artifacts Closed count with a rising Average Cycle Time reveals a productivity plateau: the user is completing work, but each item is taking progressively longer to process, often signaling accumulating complexity or organizational friction. Conversely, a declining cycle time alongside a stable Artifacts Closed count suggests process improvement rather than scope reduction.

Average Cycle Time carries a Goodhart risk: under pressure, a team can artificially reduce cycle time by closing artifacts prematurely. The Bug Reopen Rate acts as the direct counterbalance. When closures are of poor quality, reopened artifacts accumulate, and Bug Reopen Rate rises — neutralizing any apparent gain in cycle time. This pairing is what makes Average Cycle Time a defensible indicator rather than a gameable one.

Commitment and quality

Sprint Completion Rate measures the share of sprint-committed artifacts a user closed by the end of the sprint. Bugs Resolved isolates the subset of closed artifacts that were bug-type items. Bug Reopen Rate measures the proportion of those bug closures that were subsequently reopened.

Sprint Completion Rate is the commitment accountability indicator: it captures reliability, not raw output. A user who commits to ten items and closes ten demonstrates a different capacity than one who commits to twenty and closes twelve, even if the raw Artifacts Closed count favors the latter. Sprint Completion Rate carries a gaming risk through story-point inflation — artificially small commitments always close. Reading it alongside Artifacts Closed exposes this: a perfect Sprint Completion Rate with a low Artifacts Closed total is the signature of conservative commitment, not high performance.

Bugs Resolved and Bug Reopen Rate form a quality pair that serves a distinct purpose from the delivery pair. Bugs Resolved is meaningful specifically for teams with dedicated quality or on-call responsibilities; in a team where bug resolution is shared informally, it is less discriminating. Bug Reopen Rate reads across both quality dimensions: a high rate on a user who closes many bugs is more alarming than a high rate on a user who handles few, because the absolute exposure to poor closures is larger.

Backlog health

Average Backlog Age is the only leading indicator in the set. It measures the average age of open artifacts assigned to a user — items that have been created and assigned but not yet closed. A rising Average Backlog Age does not indicate that the user is unproductive; it indicates that items are waiting, whether for dependencies to clear, for priority reassignment, or because of unresolved blockers. This distinction matters for management: Average Backlog Age drives a conversation about what is stuck and why, before the delay translates into a missed sprint commitment or an inflated cycle time.

Scope and limits of the integration

Tuleap trackers are fully configurable per organization. Field names for status, type, and assignee vary per tracker and per customer instance. This integration relies on the contributor semantic — a first-class Tuleap concept identifying the field that carries ownership — rather than hardcoded field names. Organizations that have not configured the contributor semantic on their trackers will not produce attributable data. The coverage of these KPIs is therefore conditional on the quality of tracker configuration on each customer's instance.

More broadly, Tuleap records status transitions and assignments but does not capture the quality of the work produced. An artifact closed as done may represent a thorough implementation or a minimal patch; the API data does not distinguish between the two. Sprint Completion Rate reflects commitment discipline, not the value delivered. Bug Reopen Rate is a proxy for closure quality but cannot detect issues that should have been filed and were not. The reliability of all six KPIs depends directly on how consistently teams use Tuleap statuses, types, and contributor assignments — rigorous practice strengthens the signal; inconsistent practice degrades it.