This Historical Activity Stats is our #1 recommended page to establish a sense for how the company's long-term fortunes are unfolding. As will be shown below, this elements on this page offer clarity as to whether the team's velocity is growing or shrinking over time.
As with most all pages on GitClear, this page can be setup to filter on any combination of:
The first graph shown on the page is called "Stats Historical View" and by default it shows how Line Impact per repo is changing over time:
Stats Historical View graph showing how much Line Impact has accrued to 10 different repos during the past year
Hover over any data point to get a detailed breakdown:
Hover on a data point in the Stats Historical Graph to get a detailed breakdown of its constituents
You can also use the download icon to the right of the graph's title to download all of this data into a CSV file.
Aside from the main Line Impact graph featured upon clicking into the Historical Stats page, there are three more graphs available to Pro subscribers:
Code Breakdown graphs allow exploring code progress based on various dimensions. Click the chart title to have the Code Breakdown graph promoted to become the featured graph on the page
Breakdown by Provenance. Indicates the length of time since the code was last modified in a meaningful way. Strong teams ensure that they get a mix of adding new code and revising or removing old code
Breakdown by Operation. Includes Added, Updated, Deleted, Find Replaced
Breakdown by Code Domain. The category of code that was impacted. These values change based on your Code Categories.
By clicking on the title of any chart from the "Code Breakdown" section, that chart will be promoted to the featured graph on the page. This will make the chart 3x larger and increase the number of segments from 5 to 10. It will also avail the detailed tooltips shown in the section above.
This graph shows how much Line Impact has been accumulated per hour over the time you've selected. Note that this graph does not simply count up how many commits were made each hour, like more naive "hour graphs" offered by competitors. Instead, the Hourly Line Impact graph uses factors in the duration of each commit to spread that commit's Line Impact across the span of time in which that commit took place.
For example, if a developer takes four hours to make a 100 Line Impact commit at 3pm, then the Line Impact graph would attribute 25 Line Impact for each hour in the range from 11am-3pm (the full length of time the developer was authoring the commit).
This graph is most useful when seeking to understand the impact of routinely scheduled meetings or events on developer productivity. The lighter blue areas (that fall within business hours) indicate productivity being lost to external factors. A good manager can intervene to eliminate any hours of the week that consistently produce less productive outcomes.
The punch card will show which days have the most active during the period selected. The radius of each circle on the calendar corresponds to the relative Line Impact for that day. Hovering over the circle will provide the number of commits and total Line Impact on the combined days during that period.